Quote:
Originally Posted by knc1
Not only does it take a lot of resources to compute a large font the first time, it requires a lot of memory space for the font cache.
|
If you're referring to the fontconfig font cache, you can't render any fonts without that in place already, so if your Kindle is displaying anything resembling text, you already have the fontconfig cache in place.
I'm not aware of any other aggressive work done by fontconfig or freetype: fonts are rendered lazily, as required, so the size of a font or the number of glyphs has little effect on performance (though very complex single glyphs might still slow things down a bit). The last system I'm aware of to do aggressive computation of anything much relating to every glyph in a large font was X11 core fonts, and the Kindle doesn't use those. It's a lethally bad idea with modern Unicode fonts with many thousands of glyphs. It was fairly common to see X servers lock up for minutes at a time back then.