Active Topics
-
How many of you still use N900 as main phone? (595)
to Community by deutch1976 - 1 day, 15 hrs ago -
Big news (7)
to OS2008 / Maemo 4 / Chinook - Diablo by endsormeans - 3 days ago -
Firefox with Leste (8)
to Maemo 7 / Leste by endsormeans - 3 days ago -
Which is the best N95? What software modifications could be made to it? (3)
to General by Kalatti - 6 days, 1 hr ago -
Installing CSSU Stable in year 2024 (2)
to Maemo 5 / Fremantle by teroyk - 6 days, 8 hrs ago -
Porting apps to Leste (34)
to Maemo 7 / Leste by Arno_11 - 6 days, 18 hrs ago - more...
 |
|
2009-04-05
, 03:25
|
|
Posts: 693 |
Thanked: 502 times |
Joined on Jul 2007
|
#2
|
You might try :
http://maemocjk.garage.maemo.org/
It may mess with input methods so if your on n800 be prepared to reflash if it messes up virtual keyboard.
http://maemocjk.garage.maemo.org/
It may mess with input methods so if your on n800 be prepared to reflash if it messes up virtual keyboard.
 |
|
2009-04-05
, 04:43
|
|
Posts: 221 |
Thanked: 43 times |
Joined on Oct 2007
@ Sendai, Japan
|
#3
|
I will give that a try and let you know how it comes out.
 |
|
2009-04-06
, 06:53
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#4
|
Most likely the encoding of the filename isn't UTF-8, but EUC or SJIS.
UTF-8 filenames should display correctly in the filemanager and media player.
If the names in the screenshots are not filenames, but ID3 tags, you should use ID3v2.3 or ID3v2.4 tags because those support character encodings. ID3v1 doesn't know about encodings.
UTF-8 filenames should display correctly in the filemanager and media player.
If the names in the screenshots are not filenames, but ID3 tags, you should use ID3v2.3 or ID3v2.4 tags because those support character encodings. ID3v1 doesn't know about encodings.
|
|
2009-04-06
, 06:55
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#5
|
Oh, and don't worry about Diablo. Maemo supports CJK fonts since Diablo out of the box without having to install additional fonts.
|
|
2009-04-07
, 16:43
|
|
Posts: 8 |
Thanked: 3 times |
Joined on Feb 2009
|
#6
|
Originally Posted by pycage
The default diablo Media Player shows MP3 tags instead of file names in the 'now playing' and file selector screens. Unfortunately, the program does not use correct encoding, as my all my MP3 tags are ID3v2.3 and does not display correct japanese, korean or chinese characters within those tags.
Most likely the encoding of the filename isn't UTF-8, but EUC or SJIS.
UTF-8 filenames should display correctly in the filemanager and media player.
If the names in the screenshots are not filenames, but ID3 tags, you should use ID3v2.3 or ID3v2.4 tags because those support character encodings. ID3v1 doesn't know about encodings.
Canola and Mediabox display japanese characters correctly out of the box but the korean and chinese characters needed a unicode font or corresponding korean and chinese font in my /~/.fonts directory.
Does Nokia 'Media Player' have the source available to recompile with correct UTF-8 settings? OR is it closed source?
Last edited by marsteam; 2009-04-07 at 16:44. Reason: fixed directory
|
|
2009-04-07
, 18:46
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#7
|
Unfortunately the Nokia Media Player is closed source.
ID3v2.3 supports the encodings latin-1 (irrelevant for CJK), utf-16 (little and big endian), and utf-8. Maybe the Nokia Media Player doesn't look at the encoding flag and just assumes UTF-8. This would totally mess up UTF-16 encoded stuff.
I don't know about Canola, but MediaBox displays Japanese and Chinese characters out of the box on Diablo. I don't know about Korean, either, since I currently don't have music with Korean tags.
I assume the Nokia Media Player shouldn't have problems with font rendering either. It could be the encoding problem there.
ID3v2.3 supports the encodings latin-1 (irrelevant for CJK), utf-16 (little and big endian), and utf-8. Maybe the Nokia Media Player doesn't look at the encoding flag and just assumes UTF-8. This would totally mess up UTF-16 encoded stuff.
I don't know about Canola, but MediaBox displays Japanese and Chinese characters out of the box on Diablo. I don't know about Korean, either, since I currently don't have music with Korean tags.
I assume the Nokia Media Player shouldn't have problems with font rendering either. It could be the encoding problem there.
|
|
2009-04-07
, 19:00
|
|
Posts: 8 |
Thanked: 3 times |
Joined on Feb 2009
|
#8
|
Originally Posted by pycage
Interesting... I use MP3tag to clean up my files, and haven't played with the ID3v2.3 encoding differences between UTF-16 and UTF-8... I never had to as my dedicated mp3 player (Samsung P2) displayed everything correctly. I will play around with the program settings and see if I can get it to encode as UTF-8 instead of UTF-16.
Unfortunately the Nokia Media Player is closed source.
ID3v2.3 supports the encodings latin-1 (irrelevant for CJK), utf-16 (little and big endian), and utf-8. Maybe the Nokia Media Player doesn't look at the encoding flag and just assumes UTF-8. This would totally mess up UTF-16 encoded stuff.
I don't know about Canola, but MediaBox displays Japanese and Chinese characters out of the box on Diablo. I don't know about Korean, either, since I currently don't have music with Korean tags.
I assume the Nokia Media Player shouldn't have problems with font rendering either. It could be the encoding problem there.
Regarding Chinese characters, I believe that system-wise there is display support for Japanese and Simplified Chinese but not Traditional Chinese characters; Just to be safe I threw in a full Unicode font to solve the problem and gain other character sets for the browser.
|
|
2009-04-07
, 19:24
|
|
Posts: 8 |
Thanked: 3 times |
Joined on Feb 2009
|
#9
|
I see in MP3tag there are these options:
ID3v2.4 UTF-8
ID3v2.3 UTF-16
ID3v2.3 ISO-8859-1
All my files (ALL OF THEM *sob*) are encoded in ID3v2.3 UTF-16...
Testing the same S.Korean mp3 in both ID3v2.4 UTF-8 and ID3v2.3 UTF-16 encoding: Both files show garbage characters in the Media Player. Mind you, they are DIFFERENT random characters for the exact same song, but random garbage characters nonetheless. Oh well, no need to re-encode my whole library.
ID3v2.4 UTF-8
ID3v2.3 UTF-16
ID3v2.3 ISO-8859-1
All my files (ALL OF THEM *sob*) are encoded in ID3v2.3 UTF-16...
Testing the same S.Korean mp3 in both ID3v2.4 UTF-8 and ID3v2.3 UTF-16 encoding: Both files show garbage characters in the Media Player. Mind you, they are DIFFERENT random characters for the exact same song, but random garbage characters nonetheless. Oh well, no need to re-encode my whole library.
|
|
2009-04-07
, 21:01
|
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#10
|
All my music is tagged with ID32.4 UTF-8 tags and the Chinese ones still show up as ???? in media player. But I rarely use it (I prefer youamp, canola, or mediabox) so it works out anyway.
__________________
Originally Posted by ysss
They're maemo and MeeGo...
"Meamo!" sounds like what Zorro would say to catherine zeta jones... after she slaps him for looking at her dirtily...
Anyways, up until this point I have been using the default media player on my n800 and I have been happy with it. I have recently moved to Japan and since I am in the process of learning Japanese I have been listening to a lot of Japanese music. In any event, I have found that the default media player in diablo doesn't like Japanese font.
SCREENSHOT!!!
SO what do you guys think? Is there a module I can install for Japanese font? I know my way around my n800 so I am not afraid of technical instructions. Thanks.