MobileRead Forums - View Single Post - FW 5.3.x

NiLuJe · 06-23-2014, 06:18 PM

@jacobt13: Okay, good

.

Just to be sure, a couple more questions:

* You overrode the Serif family with Droid Serif, correct? Once you've restarted the framework, in the Aa menu, that means "Caecilia" (not the condensed version) should now be Droid Serif (that should be visible from the Aa menu itself, the font will still be shown as named Caecilia, but rendered as Droid Serif).
That reminds me that I should add a screenshot to make that clear

. [EDIT: Done, see #2. I took the opportunity to update the KUAL screenshots, too.)

* I'm assuming the Publisher Font actually renders as the font the publisher intended, and not one of yours?

But to answer your question, yeah, KF8 font embedding is tied to the book file itself, it has no bearing on the device it's actually read on (any KF8 capable Kindle app handles embedded font this way), so if the workflow (and the slightly larger files), and more importantly how that renders on your device of choice, suit you, by all means, it's a perfectly valid solution

.

EDIT: Oh, that reminds me: there's a (couple of different) bug(s) in some badly formatted files using embedded fonts (and even a couple when not using embedded fonts) where the font choice you make in the Aa menu isn't actually honored, and either falls back to Caecilia or Helvetica. You might want to check a different book (preferably *without* embedded fonts) if things still feel wonky

.

06-23-2014, 06:18 PM	#206
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	@jacobt13: Okay, good . Just to be sure, a couple more questions: * You overrode the Serif family with Droid Serif, correct? Once you've restarted the framework, in the Aa menu, that means "Caecilia" (not the condensed version) should now be Droid Serif (that should be visible from the Aa menu itself, the font will still be shown as named Caecilia, but rendered as Droid Serif). That reminds me that I should add a screenshot to make that clear . [EDIT: Done, see #2. I took the opportunity to update the KUAL screenshots, too.) * I'm assuming the Publisher Font actually renders as the font the publisher intended, and not one of yours? But to answer your question, yeah, KF8 font embedding is tied to the book file itself, it has no bearing on the device it's actually read on (any KF8 capable Kindle app handles embedded font this way), so if the workflow (and the slightly larger files), and more importantly how that renders on your device of choice, suit you, by all means, it's a perfectly valid solution . EDIT: Oh, that reminds me: there's a (couple of different) bug(s) in some badly formatted files using embedded fonts (and even a couple when not using embedded fonts) where the font choice you make in the Aa menu isn't actually honored, and either falls back to Caecilia or Helvetica. You might want to check a different book (preferably without embedded fonts) if things still feel wonky . Last edited by NiLuJe; 06-23-2014 at 08:52 PM.