Quote:
Originally Posted by PenguinCEO
The problem is not the effort. The problem is that
Code:
font-family: monospace;
is standard CSS, and if kobo doesn't recognize that directive it has to be considered a bug. Sideloading external fonts and patching up the firmware is not a solution as far as setting a standard directive into an epub means to make a not-portable ebook. |
Hmm... looking at the xhtml code tag: "
The code tag is designed to display computer code in a special font, usually in a mono spaced font style. However, the exact appearance will be browser dependent. You may still need to use various HTML tags, such as br and p, to create a presentation and appearance to suit your needs."
To quote: "
reading systems are not required to provide the fonts necessary to display every unicode character, though they are required to display at least a placeholder for characters that cannot be displayed fully" (Open Publication Structure 2.0.1).
So are we confusing "usually" with "must"? Or requiring a reading system to support all fonts? Neither of these is required so where does the "bug" come in.
If you are truly worred about sideloading or patching, then embed the monospaced font in your ebook. Though I fail to see how patching the software on your Kobo makes a non-portable ebook -- you haven't modified the ebook.