MobileRead Forums - View Single Post - Help

NiLuJe · 11-26-2010, 08:47 PM

Still no idea why some Kindles (FW 3.x only) fail to load some fonts... The only time that ever happened to me, that was with the *default* fonts (ie. Caecilia), and it worked fine 5 minutes later. >_<".

But, using a freetype override (bci or autohint) seems to 'fix' it, so my guess would be a weird freetype bug/interaction bug with the Java framework in the specific freetype version (or paches?) bundled with FW 3.x. That doesn't really explain why it only happens on some Kindles, though.... -_-"

EDIT: Yep, a straight Kindle to Kindle copy of a DRM'd book would explain the PID mismatch

.

11-26-2010, 08:47 PM	#16
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	Still no idea why some Kindles (FW 3.x only) fail to load some fonts... The only time that ever happened to me, that was with the default fonts (ie. Caecilia), and it worked fine 5 minutes later. >_<". But, using a freetype override (bci or autohint) seems to 'fix' it, so my guess would be a weird freetype bug/interaction bug with the Java framework in the specific freetype version (or paches?) bundled with FW 3.x. That doesn't really explain why it only happens on some Kindles, though.... -_-" EDIT: Yep, a straight Kindle to Kindle copy of a DRM'd book would explain the PID mismatch . Last edited by NiLuJe; 11-26-2010 at 08:51 PM.