MobileRead Forums - View Single Post

NiLuJe · 10-01-2013, 01:49 PM

@Katsunami: Which is exactly what I was thinking of, except you can replace 'broken' by 'random', because I've had perfectly valid (and simple) fonts make Amazon's FreeType crash/loop, basically badly mess up. Couple that with the "3 strikes and you're out" behavior of the boot process, and that makes for a shiny luminous paperweight in record time.

And then if you actually use a proper FreeType build from upstream's sources, it magically works without a hitch... So, yeah, not surprised they didn't bother to implement it in a saner way, and just killed it outright, because a wide release as is would be a mess to support.

10-01-2013, 01:49 PM	#150
NiLuJe BLAM! 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	@Katsunami: Which is exactly what I was thinking of, except you can replace 'broken' by 'random', because I've had perfectly valid (and simple) fonts make Amazon's FreeType crash/loop, basically badly mess up. Couple that with the "3 strikes and you're out" behavior of the boot process, and that makes for a shiny luminous paperweight in record time. And then if you actually use a proper FreeType build from upstream's sources, it magically works without a hitch... So, yeah, not surprised they didn't bother to implement it in a saner way, and just killed it outright, because a wide release as is would be a mess to support. Last edited by NiLuJe; 10-01-2013 at 01:53 PM.