Quote:
Originally Posted by JSWolf
The ePub does not set a font/font style formost of the main text. That's not an issue.
|
That is untrue. Most of the paragraphs in that book use class x04-Body-Text which according to the CSS you posted includes font-family: serif.
Quote:
Originally Posted by JSWolf
It's where they use sans-serif and monospace that you miss out in the KF8. The sans-serif you can lose and not be an issue. But the monospace is used for messages.
|
I agree. Losing the monospace font causes the text messages to no longer stand out.
The discarding of all font selections from the KF8 format by Amazon appears to have been triggered by the publisher's setting a font style (serif, sans-serif, or monospace) for
every paragraph in the book.
Quote:
Originally Posted by Tex2002ans
Hmmm, but what if they used @media in their files to direct slightly different CSS for each Amazon version.
Doesn't Amazon interpret the @media, then generate new CSS per each (MOBI + KF8 + KFX)? Or does it still carry the same CSS over to all 3 versions?
|
Only the effects of media queries appear in MOBI and KFX since neither format really supports CSS. However media queries are carried over into KF8 format, so if the publisher was doing that it would be visible there. It is not in this case.
Quote:
Originally Posted by salty-horse
I may be confused about what "KF8" is. I only know of the KFX bundle, and AZW3. Which one is considered KF8?
|
KF8 (kindle format 8) is Amazon's name for the format that calibre calls AZW3.
Quote:
Originally Posted by salty-horse
What do you mean by "monospace font"? Just the font-family: monospace style?
|
Yes.
Quote:
Originally Posted by salty-horse
I don't care about that, since I replace these with a computery non-monospaced font.
|
It's really old-school to associate text messages with a monospace font. I personally would have chosen italics for that in this book.