Droid Sans with a cut musical note!

Fonts! Yes, one of S60′s oldest mysteries. Why Euro1 firmware phones don’t support asian fonts? It made sense back in the S60v2 times, where memory was scarce. But now there’s plenty of space for just a couple more megabytes that a full unicode font would occupy.

For that, there are alternative fonts, pretty much any .ttf you find, with a little magic, it can be used as a system font. If you want a wider range of characters, you have two options:

Nokia's own Heisei Kaku Gothic S60

or

Any other unicode font you find, for example, Arial MS Unicode

Thing is, the latin letters from Heisei Kaku are quite ugly, in my opinion. (and I’m not the only one, I’ll add some quotes here later :P). And regular fonts are just too big/wide  for mobile phones, they’re not designed with small UIs in mind. Compare with regular Series S60 Sans.

lol blocks

So what could I do to fix that? Enter FontForge! An free multiplatform font editing application. I finally figured out how to “merge” fonts using it.

You can take s60snr.ttf from Z:/System/Fonts and use FontForge to merge any font with japanese characters to it, fontforge will import the characters the original font does not have, so you keep the regular S60 latin letters, adding Japanese support to it.

Open both fonts on fontforge. (it asks me if I want to import bitmap fonts for heisei, I just answered no.)
On the s60***.ttf window, on the menubar, Element > Merge fonts. I get this:

Found on Element > Merge

After it merges (practically instantly), on the S60***.ttf window I go Files > Generate fonts. Uncheck the Validate Before Saving option or else fontforge will complain.

Even the font that comes with S60 won't properly validate, so uncheck that.

On the screenshot on the top of the post, however, you see a different font than the standard S60 font. That is Droid Sans (download link), the font used on Google’s Android platform. I got it because I thought it looked kinda neat, as an example for this post. But one thing you don’t have in other fonts, are the characters specific to S60. For example, the space bar symbol, the line break symbol, the cut musical note that indicates the phone’s on silent profile, etc.

There they are, hidden in U+F800

Again, you can import those characters with FontForge, so now you can add those UI elements to every font you want to use on your phone.

Now to apply those fonts to your font, you need an application called FontRouter LT to avoid doing the whole renaming and copying procedure font changing used to take, and to make it even more simple, there’s an application called FontRouter Man, so you can turn it on and off with a single menu option.

FontRouter Man's default settings

Now, for the downloads:

• FontForge (pick your OS)
• HeiseiGothS60.ttf (the original Nokia japanese font, I’m not sure if I can host it here, but it’s easily available around if you search.)
• FontRouter LT (the latest version)
• FontRouter Man (the version that worked on my 5800)

Take this post as 10% tip in adding Nokia characters to other fonts, 90% report of my “research”. I’ll try to update it in case I figure out how to add different variants of S60 Sans in FontRouter for the closest default UI look. That or if I figure how to make a lighter mix of the Droid Fonts in order not to crash the phone with arabic.

Update!

So I figured out why modifiying the three variations of S60 Sans wouldn’t please FontRouter.

Tricky.

Both the regular and the SemiBold version have the same name! That’s why when adding s60snr, s60ssb, and s60tsb to FontRouter, just the regular and the title font would be added.

Notice all three variants: Red uses s60tsb, blue uses s60snr and the list uses s60ssb.

So this puts a conclusion to why I couldn’t use FontRouter to get the closest default UI look. I had to change the fonts the old school way, copying all three modified .ttfs to E:/Resources/Fonts and rebooting. Now I’m considering moving those files to C: (as leaving them on E: breaks mass storage mode (files in use, y’know)). Keep in mind deleting fonts after you added them on E:/Resources/Fonts requires you to boot up without the memory card (to free the files). Hopefully nothing will break, and I’ll be able to have the same fonts as I used to have, with nothing broken, just with added Japanese support.