Quote:
Originally Posted by AliceWonder
Readers without monospace fonts are an unfortunate decision because there are legitimate reasons for publishers to use them where a variable-width font does not give the atmosphere to the reader.
|
Yes, but this is why you lay down multiple fallbacks, just in case.
HTML:
Code:
<p>To open the Index Editor select the menu item <span class="menuitem">Tools→Index→Index Editor</span> or its keyboard shortcut:</p>
CSS:
Code:
span.menuitem {
font-family: monospace, courier, sans-serif;
font-size: .9em;
}
If the reader doesn't support monospace, then it will turn sans-serif. And if anything, it'll be a slightly smaller font size than the surrounding text.
IF the device then doesn't support embedded fonts, doesn't have monospace, doesn't have sans-serif, doesn't even support CSS (and doesn't apply/overrides your small font size)... THEN maybe you can shrug your shoulders and say you tried your best... and tell them to stop using Moon+ Reader.
Quote:
Originally Posted by Hitch
It has to do with years of experience, in making hundreds and thousands of books, on untold numbers of devices, and seeing everything that can, and does, go wrong.
[...]
As I tried to explain, initially, I have no issue with them when used in a limited way. As long as they aren't used for the reading material, by and large, hey--your book.
|
The thread is called "Font Best Practices", so we give out the best practices to make the books work across all readers, with proper fallbacks...
But no, no... fight the advice tooth and nail from those who made hundreds/thousands of books tested across dozens of devices from all form factors.
