Quote:
Originally Posted by geormes
Embedded fonts are fonts used in the epub file and are NOT resident on the ereader? If an ereader does not display the embedded font this is counted as a bug? If the epub code passes through a checker of some sort it is counted as being well-formed?
|
Yes
Matter of oppinion currently
I'm sure people have yet to invent all kinds of badly put together e-pubs that the checkers don't catch.
Quote:
|
2. I see the font file is declared in the opf manifest and placed in the same directory. Will some ereaders still display the embedded font if it is not done in this manner and will it pass the checkers?
|
I don't really know, but probably.
Quote:
|
I am a complete novice when it comes to this sort of thing. I have seen code using the @font-face method then telling CSS to use it in the whole document with the body method. Then it was claimed that because this didn't work on a Kobo the device firmware had a bug. For this to be true wouldn't you have to verify the opf manifest was correct also? I'm not saying this is the case but would it be a "bug" if only OpenType worked?
|
It's not a problem with manifest or font type.
As far as I can tell, Kobo implements user selectable font by appending a body {font-faily: "User Selected Font";} (as well as other applicable parameters. If you want a font to work on the whole document in Kobo, put the parameters in a class.
Example, in css .styling {font-family: "My font";}
In the individual html/xml files: <body class="styling">