Quote:
Originally Posted by frankieGom
OK, now that I understand the issue a little better, I need to ask: How should one go on about displaying the fonts as defined in the epub (apart fro making sure the specific font is available in the reader)?
Should there be an option in the reader to over-ride user choice and use embedded fonts if available?
|
rashkae is wrong, what he sees as a feature is 100% a bug. Kobo is doing it wrong. And I know it can be done correctly. the nook STR supports ePub font overriding and when the ePub has an embedded font and it's enabled using font-family in the body style, it displays unless it's overridden by the custom settings. So if B&N can do it, Kobo can too.
When a publisher embeds fonts in an ePub, 99% of the time, the main font used is enabled via an entry in body such as...
body {
display: block;
font-family: "charis";
}
What should happen is that ADE should use whatever font is defined to the definition of charis. In this case, it would be Charis SIL. Other readers would display the correct font on screen. Kobo ignores this because they have a bug in the font handling. If you look at any of the the new Star Wars eBooks, they come with Charis SIL as an embedded font. B&N, Sony, ADE for Windows or MAC, Pocketbook, and others will display Charis SIL. Kobo will not. Why not? Because it's a bug in the Kobo version of ADE.