View Single Post
Old 09-21-2010, 08:09 PM   #572
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
@911jason: That's it. It's not removed when you install (or when you uninstall, for that matter) the hack, so it's still there, and your scrensavers are still randomized .

@all: Hurray. Fonts v3.8.N. K3 support!

I advise those especially interested to tweak the International fonts, and the browser fonts to read the first post, a few things have changed .

Namely:

* The K3 renderer uses TrueType bytecode hinting instructions. Fonts that have nice hinting instructions will look very sharp, while fonts with no/crappy bytecode will look fuzzy, especially at small sizes. The upside is that, finally, full Serif fonts can look fantastic, provided they've got good hinting code.

* The K3 uses a bunch of auxilliary fonts for CJK/International scripts. I simplified this a bit. There's two new custom fonts:

CJK.ttf: For Chinese/Japanese/Korean (Droid Fallback by default)
I18N.ttf: Everything else (DejaVu Sans by default)

* The browser uses fontconfig to pick the fonts. For those familiar with it, you know it uses a very powerful XML config, and uses a cache of available fonts to speed things up. While the config part of things is not such a problem for us, the cache is. On the tiny Kindle CPU, it takes approximately 5 minutes to regenerate this cache!
Because of this, handling the browser fonts is disabled by default. Check the first post if you want to try it (it works, it just takes a crapload of time each time you switch fonts ^^).

EDIT: And MR Wiki updated. (Without the nobrowser spiel, to avoid being way too confusing)

P.S @mods: Would it be possible to change the title of the thread to "Fonts & ScreenSavers hacks for Kindle 2.x & 3.x" please? Thanks!

Last edited by NiLuJe; 09-21-2010 at 08:20 PM.
NiLuJe is offline   Reply With Quote