View Single Post
Old 05-03-2011, 01:53 PM   #774
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@meme: You can also use OpenType fonts, they're working fine (I'm actually mostly using OpenType CFF fonts right now ), but they'll have to follow the naming scheme (ie. .ttf, even if they're not truetype fonts at all).

I didn't touch the alt settings in the fonts hack, so it should work fine with the fonts hack installed, too .

As for a way to verify the Kindle framework won't die horribly on a specific font, welcome to the club . I don't even fully understand *why* it breaks, because the exact same font will work fine on a Kindle, and break horribly on another one, with the exact same FW... It does seem to be linked to the freetype lib bundled on the K3, since using a custom one has so far 'fixed' it for a lot of people, if not everyone encountering this issue with the fonts hack...
NiLuJe is offline