Support and General Use > Theming and Appearance Customization

How do I use/select specific characters from a font map?

(1/4) > >>

bascule:
I've been looking at the font maps on rasher's site (specifically nimbus-12 [link]), but I don't understand how to generate any given character.

For example, I want to to use the Greek Xi (Ξ) character in a WPS, but when I use that character in the WPS file (inserted using Window's 'Character Map' utility), it just displays on the screen of my H120 as the default dotted rectangle character (top left on the font map).

I presume this is because the rockbox fonts are a subset of the full character set.

How can I determine what ?unicode/ASCII? character code relates to a position in the font map and then how could I use Notepad++ to cause that character to display properly in my WPS?

pixelma:
You would have to save the wps file in utf-8 format.

In Notepad++ there is a setting for doing so... go to menu: "Format" -> "Encode in UTF-8"- it's best to also choose "UTF-8 without BOM" (at the moment). While I did not have any problems with these ByteOrderMarks (a specific "sign" at the beginning that defines the text as being utf-8) in wps files, it was found that having it in fmr-files keeps rockbox from reading the first entry (the same line where the BOM is at).

To save it as utf-8 will also make tags that includes these characters work properly in the wps with the right font.   :)

Edit: As for determing what fonts include which character set you can have a look here... http://www.rockbox.org/twiki/bin/view/Main/UnicodeFonts. Other than that I do not now where else you can look but I just tried your "Xi" example with a wps using nimbus-12 and it works when saved correctly...

bascule:

--- Quote from: pixelma on January 15, 2007, 07:19:21 AM ---...it was found that having it in fmr-files keeps rockbox from reading the first entry (the same line where the BOM is at).

--- End quote ---

I had the same problem with custom tagnavi files (and therefore my reason for moving to notepad++), so I'm aware of the BOM issue


--- Quote from: pixelma on January 15, 2007, 07:19:21 AM ---You would have to save the wps file in utf-8 format.

--- End quote ---

OK, did that, still no joy :(


--- Quote from: pixelma on January 15, 2007, 07:19:21 AM ---...but I just tried your "Xi" example with a wps using nimbus-12 and it works when saved correctly...

--- End quote ---

Any chance of posting it, because of course this is driving me nuts, now. I've tried it in the sim and on my H120 and I still get the default dotted rectangle character displayed.

I've also changed the sim and player's default codepage to unifont, still no luck.

EDIT: Well, it certainly does not for me.

Thanks for the Wiki link. I have now changed my player codepage back to Latin-1 and tested all the fonts listed on that page.

With my properly-encoded .wps file, I can now display the Xi symbol correctly in all fonts listed except nimbus-* and ter-*   ???

I'm confused as to what is going on here, but at least some progress is being made. The problem is back to 'which ASCII/unicode character maps to Xi in nimbus'?

This whole unicode/codepage/character set issue has done my head in for so long and despite reading the rockbox Wiki, Wikipedia and other internet articles, I'm almost as much in the dark as I was before  >:(
Anyone got a link to a simple explanation?

pixelma:
I first prepared a lengthy post when it crossed my mind that there was something about nimbus and greek and I found it in the "(cvs) changes since August"...


--- Code: ---1 Sep 13:50 | Marcoen Hirschberg | fonts/nimbus-14.bdf 1.8 | some minor changes and add support for greek
1 Sep 13:47 | Marcoen Hirschberg | fonts/nimbus-12.bdf 1.9 | some minor changes and add support for greek

--- End code ---

Together with your reference to rasher's page it leads me to the question - what nimbus-*.fnt are you using? The one from rasher's page or maybe you have an older file in your font-folder? (Please ignore the stupid question in case it was just to explain ;) ) I simply loaded the one that was in my fonts-folder (unpatched and self-compiled simulator of 23rd of December)

bascule:
pixelma, you're a star!

Your theory was correct, I had some 2006 fonts on my player. Downloaded the latest set and all is now OK. Thank you.

So, just to clear it up once and for all:

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?

And that leaves one outstanding question for me: What is the codepage setting in rockbox for?

The manual says
Default Codepage:
A codepage describes the way extended characters that aren’t available within the ASCII character set are encoded. ID3v1 tags don’t have a codepage encoding contained so Rockbox needs to know what encoding has been used when generating these tags. This should be “ISO-8859-1” but to support languages outside Western Europe most applications use the setting of your operating system instead. If your operating system uses a different codepage and you’re getting garbled extended characters you should adjust this settings. In most cases sticking to “ISO-8859-1” would be sufficient.

Am I correct in assuming that if using, as in our case, correctly coded text, it makes no difference. The codepage only comes into play if the encoding is unknown?

Navigation

[0] Message Index

[#] Next page