MobileRead Forums - View Single Post

NiLuJe · 05-11-2012, 05:52 PM

@ixtab/diba: If it's still like on the K3, check the logs when the framework throws a 'can't open this book' popup, and it will probably complain about failing to find/open/parse a font.

I have no idea how or why that happens, because a simple framework restart 'fixed' it [without switching fonts/ft engine], but it did happen to me a couple of times a whiiiile back on the K3 when playing a bit too much with the [Aa] menu and custom fonts... (I don't even remember if I had started using a custom ft lib at that time :/).

I haven't seen it since, though, but then I almost never open the Aa menu anymore

.

05-11-2012, 05:52 PM	#215
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	@ixtab/diba: If it's still like on the K3, check the logs when the framework throws a 'can't open this book' popup, and it will probably complain about failing to find/open/parse a font. I have no idea how or why that happens, because a simple framework restart 'fixed' it [without switching fonts/ft engine], but it did happen to me a couple of times a whiiiile back on the K3 when playing a bit too much with the [Aa] menu and custom fonts... (I don't even remember if I had started using a custom ft lib at that time :/). I haven't seen it since, though, but then I almost never open the Aa menu anymore .