Quote:
Originally Posted by Mathew Reuther
Be as exacting as you'd like. I am not bothered at all. I was not aware that there was a (format) argument which could even be included. Is that something you typically use? I've never seen it laid out like that. Do you recommend using that format declaration as a standard in your css? (and what is the format declaration then for truetype? "truetype"?
As for the mainifest, here is an example of what they look like. This is, mind you, auto-generated by Sigil...I do not hand code it:
(inside the manifest section of the content.opf file)
<item href="Fonts/display-font.ttf" id="display-font.ttf" media-type="application/x-font-ttf" />
<item href="Fonts/header-font.otf" id="header-font.otf" media-type="application/vnd.ms-opentype" />
Now, as a test, if you could just tell me the name of a font or two that you know will work that come from a source that is free (fontsquirrel, dafont, google fonts, etc.) I can try to use those and see what happens. That way we know that the fonts themselves DO work in another file.
|
Sure. How 'bout good old Liberation Sans? I know that works, it's a go-to for us. Also, let's see...GandhiSans-Regular (I think that's a Google font, but it might be DaFont), League_Gothic, which is a truetype (again, forget where from); OratorStd; Century Schoolbook (truetype). Those happen to be at the top of my brain at the moment, because we just did some books that had those, and I know factually all of those work at KDP. Does that help?
Those font declarations in the manifest look fine. Yes, in the CSS it's: format() with the one word type, either "opentype" or "truetype" in the parenthesis, replete with quotemarks.
What's weird to me is that you say your fonts are surviving being Genned (KG or KP); they work in your ePUBs, but somehow, they're being stripped at the KDP. That's just bloody peculiar. This has been going on for
months? You upload a working, functioning mobi with embedded fonts, and the preview is font-less? Man. That's
Hitch