Support and General Use > Theming and Appearance Customization
How do I use/select specific characters from a font map?
soap:
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?
pixelma:
Glad I could help! :D
However, I'm by no means an expert on unicode - it's just that I stumbled across the same problem with the umlauts I had in one of my first wps's. Someone in IRC gave me the hint to save the wps-file as utf-8 and it worked.
At the moment I cannot answer the questions that arose but I've become curious to understand the behinds myself now :) . So I'll try to find out some more and will report it back (as I think it can be helpful to others). Or someone with greater insight could chime in...
bascule:
Now I'm home, I've had more time to investigate this...
--- Quote from: bascule on January 15, 2007, 04:09:31 PM ---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?
--- End quote ---
Yes. And that is true not only of rockbox fonts, but Windows fonts as well. I spent some time looking through a lot of fonts on a Win2000 machine using the Character Map and they almost all contain some of the 'extended' glyphs (such as boxes and mathematical symbols), but none contained all of them.
The other thing that confused me was that on Rasher's page nimbus-12 is flagged as ISO10646-1, which put me off the unicode scent, but it appears that ISO10646-1 is a sort of unicode-lite, employing all the glyphs, but not with some of the flashy underlying abilities to combine characters or do right-to-left text rendering.
Therefore even a unicode-compatible font may not contain all possible glyphs (although rockbox's unifont does, that's why it is so huge...)
--- Quote from: soap on January 15, 2007, 07:25:18 PM ---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?
--- End quote ---
Yes. ID3v2.x can contain specified encodings. ID3v1 tags cannot contain a description of their encoding. They should therefore always be in Latin-1 encoding (ISO/IEC 8859-1), as this is what most applications reading ID3v1 will assume. However rockbox, being smarter than your average application, allows the firmware to assume a different encoding for any unspecified text, such that if you had encoded all your existing MP3s with Bulgarian language ID3v1 tags, changing the codepage would make them all legible again.
I think I've finally got my head round all this now ;D
http://en.wikipedia.org/wiki/ISO-8859
http://en.wikipedia.org/wiki/ID3
http://en.wikipedia.org/wiki/Universal_Character_Set
pixelma:
Ah... thanks for the info :)
But it still leaves me with a correction I have to make to my first post...
--- Quote from: pixelma on January 15, 2007, 07:19:21 AM ---To save it as utf-8 will also make tags that includes these characters work properly in the wps with the right font.
--- End quote ---
No - that is not true!
In case there is no codepage information given in the tags (i.e. ID3v1 standard), Rockbox will use the one defined in your "default codepage" setting to display the tags (that's what it is for - as the manual describes). Sorry for the misinformation! :-\
---
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?
bascule:
--- Quote from: pixelma on January 16, 2007, 06:22:51 PM ---
--- Quote from: pixelma on January 15, 2007, 07:19:21 AM ---To save it as utf-8 will also make tags that includes these characters work properly in the wps with the right font.
--- End quote ---
No - that is not true!
--- End quote ---
I think in essence it is true. If you want to use characters outside of Latin-1, the .wps file will have to be utf-8, otherwise the unicode character codes will not be incorporated within it. Once the .wps is correct, then it relies upon the font having the required characters in order to display them.
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've just tried re-saving my test WPS fle as ANSI, rather than utf-8 and, as expected, the screen now displays garbage where I had some of the fancy unicode graphical characters.
--- Quote from: pixelma on January 16, 2007, 06:22:51 PM ---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?
--- End quote ---
Yes. I think generally that most applications then default to displaying the 'unknown character' symbol, either a rectangle or a question mark.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version