Ticket #1136 (new Bug)

Opened 7 months ago

Last modified 6 months ago

all traks in hebrew looks like gibberish

Reported by: anonymous Assigned to:
Priority: 6, normal Milestone: To Be Decided by Jajuk Team
Component: (Jajuk Members) Any (Default Component) Version: 1.6
Keywords: Cc:

Description

there is no way to change the font to a font that can read a non Unicode language that is used on songs names (changing from UTF-8 to UTF-16 didn't help)

Attachments

gibberish.JPG (37.6 kB) - added by anonymous on 05/23/08 12:38:03.

Change History

05/23/08 12:38:03 changed by anonymous

  • attachment gibberish.JPG added.

05/23/08 12:39:18 changed by anonymous

in the picture, the files names are in hebrew, but the fonts are not hobrew fonts.

05/24/08 14:14:21 changed by bflorat

Thanks for reporting. This is probably that Hebrew fonts are not installed or not property configurated for your java virtual machine (do experience the same issue with others java programs ?).

If you're under Linux, check also http://www.jajuk.info/index.php/English_jajuk_faq#Problems_displaying_non-latin_characters

05/26/08 20:48:57 changed by anonymous

No, the tagging software used an illegal charset encoding. Unicode perfectly well supports hebrew! It is exactly because unicode was not used that the characters are not displayed correctly. Note only ID3 v2.3 or 2.4 support unicode.

05/27/08 09:03:04 changed by anonymous

I know that Unicode supports hebrew (it's a minimum as Unicode supports thousands of languages) but I thought that jre fonts were not installed but in that case, you would have get only squares, not "éùà" characters. BTW, Java only works in Unicode so jajuk obviously supports Unicode.

It may come from entagged tag reader indeed but in that case, I don't see why they are read correctly in russian for ie. Are your tags read correctly using another tool ?

BTW, note that we should switch to another tag lib in jajuk 1.7 (jaudiotagger), this may fix your problem.

05/29/08 09:22:11 changed by anonymous

If hebrew is detected for an ID3 v2.3 or v2.4 tag, Jaudiotagger will automatically use Unicode when writting. The original tag written by another (?) software however used another, illegal, charset encoding (very likely cp-1255). So either ID3 v1, v1.1 or v2.2 was used in which case only garbage will be read by Entagged/Jaudiotagger or then some other application which created the file used an encoding it shouldn't have (too often the case unluckily).

So Jaudiotagger will not fix this problem (not yet at least). More info about this issue (note that assumption of first poster is wrong: cp1251 is illegal for ID3): https ://jaudiotagger.dev.java.net/issues/show_bug.cgi?id=179


Add/Change #1136 (all traks in hebrew looks like gibberish)