Quote:
Originally Posted by Hitch
I hate to tell you this, but are you aware that when you turn on a book in a PPW family device--PPW, Voyage, Oasis--that the Publisher Font option is NOT the default and that the user has to actively turn it ON?
|
My experience with Kindle Paperwhite is a bit different. There are two very different scenarios.
If the ebook file
contains at least one embedded font, I get the "Publisher Font" option as a default. In this case, all the embedded fonts are automatically shown as intended by the ebook publisher. If there is no embedded general/body font (most ebooks use embedded fonts only for special paragraphs), then the main text is shown in Bookerly, but the special paragraphs still use the embedded fonts. If I switch to any of the other options (font names), the whole text – even the special paragraphs – uses this newly selected font and the embedded fonts are ignored.
If the ebook file
doesn't contain any embedded fonts, the "Publisher Font" option is not available in the first place. Instead, Bookerly is pre-selected as default. I can select any of the other fonts, but not "Publisher Font" since it isn't there. But even if I choose one of the other fonts, the font definitions in the css file are still honored. So when I assign e.g. 'monospace' or one of the built-in font names like 'Caecilia' to some paragraphs, these paragraphs are always shown in these assigned fonts. (But as soon as only one font is embedded, this behaviour changes.)
So if I want to make sure that my font choices for special paragraphs are honored independently of the device setting, I shouldn't embed anything and better stick with the built-in fonts.
(That's the situation with Kindle Paperwhite. ADE based e-readers like my Tolino are a different story.)