Quote:
Originally Posted by PenguinCEO
|
If I had used renderer for browser would you have been happier?
You do realize that the subset of CSS used for epub is inherited from that used by web browsers with a few minor additions?
As for Unicode, epubs are
required to use either UTF-8 (a variable width character encoding capable of encoding all 1,112,064 valid code points in Unicode using one to four 8-bit bytes) or UTF-16.
And, again to quote from the Epub specifications:
3.4 Fonts
EPUB 3 does not require that Reading Systems come with any particular set of built-in system fonts. As occurs in Web contexts, Users in a particular locale might have installed fonts that omit characters required for other locales, and Reading Systems might utilize intrinsic fonts or font engines that do not utilize operating system installed fonts. As a result, the text content of an EPUB Publication might not natively render as intended on all Reading Systems.
To address this problem, EPUB 3 supports the embedding of fonts to facilitate the rendering of text content, and this practice is recommended in order to ensure content is rendered as intended.
Support for embedded fonts also ensures that characters and glyphs unique to an EPUB Publication can be embedded for proper display.
Basically, we seem to agree that having a monospace font is desirable. Where we differ is that you want to call the lack of a monospace font a bug and are not willing to look at the workarounds that will correct the issue.
’Nuff said.