Hi, I'm a MediaMonkey user in Japan.
I chose Japan(amazon.co.jp) in Auto-Tag option.
But I can't get correct result about Japanese songs.
It seems , Amazon.co.jp sends and requires Japanese character encoded in Unicode(UTF-8).
But, MM sends to Amazon , and recognize characters as Shift-JIS code.
(Shift-JIS code is the default code in Japanese environment.)
Problem with "Auto-Tag from Amazon" in Japanese.
Moderator: Gurus
Problem with "Auto-Tag from Amazon" in Japanese.
Last edited by NiG on Wed May 24, 2006 9:51 pm, edited 1 time in total.
NiG, such problems often have something to do with your regional/language/culture/keyboard... settings on your computer.
Maybe changing these settings will solve the problem.
Maybe changing these settings will solve the problem.
Extensions: ExternalTools, ExtractFields, SongPreviewer, LinkedTracks, CleanImport, and some other scripts (Need Help with Addons > List of All Scripts).
I've corrected mistake of my 1st post.
("smiles" function worked unexpectedly)
>jiri
I know it's difficult for you to treat Japanese.
Is there something I can do for this?
At least,this problem occurred on all PCs I have.(Win2000SP4,xpSP2)
>Steegy
This is a problem of application software.
always happens on Japanese(and other multi bytes character) environment.
("smiles" function worked unexpectedly)
>jiri
I know it's difficult for you to treat Japanese.
Is there something I can do for this?
At least,this problem occurred on all PCs I have.(Win2000SP4,xpSP2)
>Steegy
This is a problem of application software.
always happens on Japanese(and other multi bytes character) environment.
To be honest, I don't know what to do about it, maybe you could try to send some screenshots with an explanation of what's displayed incorrectly.
Btw, another user reported some problem with Japanese in Amazon tagging a while ago, it was found and fixed and the user confirmed that it's working fine now. You can find it in some post here in forum.
Jiri
Btw, another user reported some problem with Japanese in Amazon tagging a while ago, it was found and fixed and the user confirmed that it's working fine now. You can find it in some post here in forum.
Jiri
screenshot : searching "My Little Lover".
Japanese strings are not readable.
I'll show what happening in following picture.
title of the album(large dotted) is "風と空のキリム".
2nd line is Hex-dump of the title encoded by Shift-JIS.
3rd lines shows same thing encoded by UTF-8.
And last line shows how looks when interpret (a) as Shift-JIS coded.
This is in agreement with a screenshot.
After all, it is thought that what is necessary is to make it deal with Japanese by UTF-8.
I found the topic
http://www.mediamonkey.com/forum/viewtopic.php?t=7324
I'm useing 2.5.2.951. is this version older?
Japanese strings are not readable.
I'll show what happening in following picture.
title of the album(large dotted) is "風と空のキリム".
2nd line is Hex-dump of the title encoded by Shift-JIS.
3rd lines shows same thing encoded by UTF-8.
And last line shows how looks when interpret (a) as Shift-JIS coded.
This is in agreement with a screenshot.
After all, it is thought that what is necessary is to make it deal with Japanese by UTF-8.
I found the topic
http://www.mediamonkey.com/forum/viewtopic.php?t=7324
I'm useing 2.5.2.951. is this version older?
Thanks for a detailed analysis, unfortunally I have no idea how should I properly work with Shift-JIS encoding.
To explain how it currently works: MM gets data from Amazon in UTF-8 encoding, decodes from UTF-8 to 16-bit wide Unicode (UTF-16) and shows it. It works well for all the languages I know. Do you have any programming reference explaining the problem of Japanese in the context of Win32 programming?
Jiri
To explain how it currently works: MM gets data from Amazon in UTF-8 encoding, decodes from UTF-8 to 16-bit wide Unicode (UTF-16) and shows it. It works well for all the languages I know. Do you have any programming reference explaining the problem of Japanese in the context of Win32 programming?
Jiri
-
Guest
I also have this problem, also when I input Japanese characters it can't search at all, only if I input English characters.I don't know how to explain it in programming terms. Is there an easier way to help out?
As for my computer, I use Japanese as my secondary language on my English Version of Windows XP.
As for my computer, I use Japanese as my secondary language on my English Version of Windows XP.
Message to Asian programmers visiting this page: please help the devs and your fellow countrymen/continentmen... 
You should know that it's a weird problem for all non-Asian people, so also not easy to solve.
You should know that it's a weird problem for all non-Asian people, so also not easy to solve.
Extensions: ExternalTools, ExtractFields, SongPreviewer, LinkedTracks, CleanImport, and some other scripts (Need Help with Addons > List of All Scripts).
-
Andres_LO
Exactly
Thank your for properly identifying this problem! I am a native English speaker, but I speak Japanese fluently and have a significant amount of Japanese music on my computer. You have no idea how hard it is to find a media player that properly recognizes (let alone can download), track information written in Japanese.
The strange thing was that for the first few weeks I had MM the Japanese recognition worked flawlessly. I could input Japanese (usually shift-js i believe) in the search box, get back properly encoded results (with track info) and update my ID3s. Now... nothing. I have no idea what happened. I am trying all combinations of regional options and MM settings.
One question. I thought that Japanese was non unicode. In fact I thought that ALL double byte character languages were non unicode. If that is the case how can amazon be returning unicode results? I thought just the opposite that I was sending out shift JS and MM was trying to convert everything to Unicode. especially since it does not support Japanese natively, but rather does so through windows libraries (is that the right term?). Am i totally wrong?
The strange thing was that for the first few weeks I had MM the Japanese recognition worked flawlessly. I could input Japanese (usually shift-js i believe) in the search box, get back properly encoded results (with track info) and update my ID3s. Now... nothing. I have no idea what happened. I am trying all combinations of regional options and MM settings.
One question. I thought that Japanese was non unicode. In fact I thought that ALL double byte character languages were non unicode. If that is the case how can amazon be returning unicode results? I thought just the opposite that I was sending out shift JS and MM was trying to convert everything to Unicode. especially since it does not support Japanese natively, but rather does so through windows libraries (is that the right term?). Am i totally wrong?
-
fuzzynavel
Me too
I have the same problem (with MM3-RC2 on Vista). MM handles Japanese characters perfectly in everything but the Amazon.jp lookup. There it chokes, and the results that come back are blank. Any non-western characters in the list of results show as empty spaces.
I was hoping with the new version this would be fixed. Bummer.
Let me know if there is anything I can do to help test or solve this problem.
I was hoping with the new version this would be fixed. Bummer.
Let me know if there is anything I can do to help test or solve this problem.
-
Guest
Because a large amount of strange character strings that cannot be made out at all are displayed,
the surprise when this bug is seen for the first time is large.
Perhaps, I think this bug is one of the big causes lowered the evaluation of MM in Japan.
Actually, many people have enumerated this problem as a dissatisfied point of MM in BBS,etc. of Japan.
Moreover, it is likely to become a differentiation that only has to be solved because Winamp has not
supported amazon.co.jp yet now.
I am using other convenient software for getting album art instead of MM for a long time.
http://team.thenexusnet.com/nexus/AAA/
This software can correctly get album arts of Japanese CDs from amazon.co.jp.
However, because the artist name and the album name are guessed based on the folder structure,
it is necessary to maintain the folder.
the surprise when this bug is seen for the first time is large.
Perhaps, I think this bug is one of the big causes lowered the evaluation of MM in Japan.
Actually, many people have enumerated this problem as a dissatisfied point of MM in BBS,etc. of Japan.
Moreover, it is likely to become a differentiation that only has to be solved because Winamp has not
supported amazon.co.jp yet now.
I am using other convenient software for getting album art instead of MM for a long time.
http://team.thenexusnet.com/nexus/AAA/
This software can correctly get album arts of Japanese CDs from amazon.co.jp.
However, because the artist name and the album name are guessed based on the folder structure,
it is necessary to maintain the folder.