View Single Post
Old 05-24-2014, 09:34 PM   #176
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
@Stunatra: In this case, I'd say yes, they weren't just being evil. Despite being undocumented, it was potentially a support nightmare, because it was basically implemented like the software version of a game of Jenga: and thus ended up one of the very easiest way to soft-brick a Kindle .

Embedded fonts (in KF8 files) are indeed much safer. At worst, you break the rendering of *the* book instead of bricking the device.

One of the purpose of this hack is to add a (thin) layer of safety around the process.

Last edited by NiLuJe; 05-24-2014 at 09:36 PM.
NiLuJe is offline   Reply With Quote