View Single Post
Old 09-30-2010, 01:26 PM   #751
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
No adverse effect, but I'd be really surprised if it actually changed anything. The font-packages-as-update way is more likely the best way to workaround this.

As for the why, you aren't necessarily the only one, some other people have had weird issues like that (Pushka, daffy4u), and that was even *before* the full hack, but with the reader.pref & alt family tweak. So, supposedly, something is way more fragile than before regarding the framework handling of font files .

EDIT: Just switched back to my usual fonts with an update pkg, still no issues.

Last edited by NiLuJe; 09-30-2010 at 01:32 PM.
NiLuJe is offline   Reply With Quote