Rockbox Ports are now being developed for various digital audio players!
...it was found that having it in fmr-files keeps rockbox from reading the first entry (the same line where the BOM is at).
You would have to save the wps file in utf-8 format.
...but I just tried your "Xi" example with a wps using nimbus-12 and it works when saved correctly...
1 Sep 13:50 | Marcoen Hirschberg | fonts/nimbus-14.bdf 1.8 | some minor changes and add support for greek1 Sep 13:47 | Marcoen Hirschberg | fonts/nimbus-12.bdf 1.9 | some minor changes and add support for greek
Any given unicode-compatible font is just a small selection of non-contiguous unicode characters (glyphs), which can be displayed by using the matching unicode glyphs in the WPS file.Is that correct?
Let me add further to bascule's question, for I was confused also...Codepage only matters on ID3v1 tags? Â If I have proper v2 tags for everything codepage doesn't affect me?
To save it as utf-8 will also make tags that includes these characters work properly in the wps with the right font.
Quote from: pixelma on January 15, 2007, 07:19:21 AMTo save it as utf-8 will also make tags that includes these characters work properly in the wps with the right font.No - that is not true!
Just another thing that I found while I was searching for information about ID3v2 specifications: paragraph 3.2 in http://www.id3.org/id3v2-00 states about ID3 tags..."If nothing else is said a string is represented as ISO-8859-1 characters in the range $20 - $FF."Is it safe to say that there could be problems with characters out of the said ISO-8859-1 range if the tag-program messes things up?
The codepage option is a kind of safety net underneath all of that to allow ID3v1 strings without the embedded character encoding information to be handled correctly.
I retagged some of the songs as ID3v2.3 using "The GodFather" and "Multi ID3 Tageditor" and got the same results as described above.
Did you change [menu]>General Settings>Playback>ID3 Tag Priority?
the tags showed the "box" with the wrong default codepage - they were correct with the right codepage setting.
Quote from: pixelma on January 16, 2007, 06:22:51 PMIs it safe to say that there could be problems with characters out of the said ISO-8859-1 range if the tag-program messes things up?Yes. I think generally that most applications then default to displaying the 'unknown character' symbol, either a rectangle or a question mark.
Is it safe to say that there could be problems with characters out of the said ISO-8859-1 range if the tag-program messes things up?
Page created in 0.082 seconds with 21 queries.