Quote:
Originally Posted by AliceWonder
...
My basic philosophy is to use fonts that match the purpose and are as friendly as possible while clearly commenting the .css file to make it easy for the end user who needs to change them to do so.
e.g.
Code:
/* This color emulates the classic pulps - feel free to nuke
* this if it bothers you...*/
body {
background-color: #EBE8D9;
}
/* This is the font used for most of the content. If you need
to change it to make the book readable for YOUR eyes, this
is where. Just removing the font-family line should result
in your reader default font being used instead, or you can
specify an alternate font installed on your system. */
article p {
font-family: 'Clear Sans', sans-serif;
widows: 2;
orphans: 2;
}
...
Whatever font works best for someone, comment the CSS so that it is easy for those who want to modify it to do so. That's my philosophy. Everyone has different reading preferences. Some may want Times just because they like Times, for example. |
I think you'll find that it's pretty rare for individuals to know how to change the css in their books (MR readers excepted)...and even more rare for those to care to take the time to do so...
I would recommend leaving the body font undefined in your css...at worst specific titles and/or sections of text could have a font defined when it helps tell the story. Let the user choose their own font via the device settings...then everyone is happy.
Yes, Jon, I know some dinosaur devices can't display different fonts, but those are the repercussions of their device choice... They can get a newer device if font choice is a concern to them.