Quote:
Originally Posted by jackie_w
Really? My Kobo for Android only offers 'Droid Sans Serif', 'Droid Serif' or 'Publisher Default' (which I'm assuming means embedded fonts). IMO life is too short to be embedding fonts so I only have a choice of 2. Have I missed something?
|
That's right. In Kobo for Android you only can select 'Droid Sans Serif', 'Droid Serif' or 'Publisher Default'. But as you had told me that by adding
Code:
body {font-family: serif}
ruined your kobo collections, I wanted to tell you that you still could use that property without danger.
Quote:
|
On the eink Kobos, my experience has been that if you code css as body {font-family: serif} then the Kobo is able to override with the user-selectable font-of-choice stored on the device. However, if instead the font-family is in a css class (e.g. .calibren {font-family: serif; ...} after a calibre conversion) then the eink Kobo can't override and uses its default serif font (Georgia) instead of the user-selected one.
|
Yes again. Regrettably Calibre has that drawback. I use it very little, I prefer to work with Sigil since allows me a cleaner css stylesheet. In the last case you indicated, you could open the epub in Sigil and by mean of S&R to erase in classes {font-family: serif; ...} and to add it in the body selector. Of that way you could have serif font in Kobo and also in Moon+ with "Preview with publisher formatting" enabled
But all that with the only end of reading an ebook in Moon+
A lot of work
Better let's use PocketBook or Mantano
Regards
Rubén