Quote:
Originally Posted by Hitch
]If you don't care what the reader does, with the body, you should remove the body font tag. No reason for it, unless you want to force the body font to be serif (and NOT sans serif on the KF8 eInks). If you do want the body font to be other than sans, then keep the body font declaration
Secondly, don't use spans to create the font for the Fraktur.
Apply it to the correct classes, e.g, p.Fraktur, h1.fraktur, or whatever you're going to call them.
|
In this case, these aren't headings, but some words in a <p> paragraph. So they have to be spans.
And so in Kindle you have to have "Publisher Font" to see them.
And so the body font becomes sans unless I style it otherwise.
Blame the author who liked to play with typography.
(That's why I was doing this book, as an exercise to see if I could make the effects work in ebook as they did on paper, without resorting to images of text.)
Quote:
Originally Posted by Hitch
There's a definite, not-yet-fully-understood issue with fonts on Spans, in MOBI format. For one thing, there's a limit to the number of spans. I'm not sure that it's what's affecting your book, but it absolutely, positively exists.
|
But in mobi you can't change fonts at all (aside from serif/sans), I thought? Anyway, not too concerned about mobi format, though would not break it unnecessarily.
I have 21 spans in the book, most of them to make a standing cap.
Quote:
Originally Posted by Hitch
That should not be happening. Regardless of whether you choose Publisher font or not, the Fraktur should display. Try going back and applying the font on the correct elements, rather than spans, and see if the issue persists. FWIW, unless it's a one-off, at my shop, bookmakers are not allowed to use spans for fonts. Too many issues surrounding that sort of undifferentiated usage.
|
I do follow that "rule" myself. I don't use spans to style headings. Very rarely an entire paragraph of any kind.