Quote:
Originally Posted by AliceWonder
Of course users should always be able to switch the fonts to whatever works best for them. I wish ePub allowed specification of main text font in the *.opf file so that readers could over-ride it with a GUI but they don't.
|
There's no need... because CSS already do that for you.
You can just push the "font" button on your reader, and... change the font.
The problem with making the embedded font the body font is that
some devices don't let you override the publisher's font.
Which is why using embedded fonts very sparingly (Maths, signs, ornaments, headings, [...]) is be better. Those readers who can't override still get to read (the vast majority of the text) in their preferred font.
Quote:
Originally Posted by AliceWonder
(btw OT I don't know what widows and orphans options actually do, was just suggested I should have them - but in my limited testing the readers I usef seem to ignore them as I still had widows and orphans so I may remove them)
|
widows/orphans are the amount of lines at the bottom/top of pages, making sure you don't get something like this:
Code:
This is a longer paragraph at the
end of a superduper extra longer
[Flip page]
page.
Just remove the widows/orphans in your CSS, there's no need for your to specify, devices have their own defaults.
Note: Although before JSWolf posts... he prefers widows/orphans to be set at 1 for ebooks, so that if there's space for it, the ebook always shoves a line there.
Note #2: Be careful with setting background color, that potentially interferes with Night Mode on many devices (or may look atrocious on e-ink). Again, most color devices/readers have settings that can do that for you, and readers choose their own background+text color preferences.