Quote:
Originally Posted by DiapDealer
I don't upload the epub to Amazon, so the epub.css is never even a factor. I upload the combination mobi/KF8 that I build from the epub, so with the "@import url(../Styles/epub.css);" line commented out in the main css file, KindlePreviewer/Kindlegen ignores the epub.css file it during its build process. The commented-out line still appears in the main css file whenever the KF8 is unpacked and inspected, but that's the extent of it.
|
Great answer! I've been playing with various ways: a main stylesheet with Kf8 and mobi tweaks or overrides (as done in the KF8 samples on Amazon), or using not-mobi for the main stylesheet so that the main stylesheet has formatting for both ePub and KF8 with a standalone for Mobi, or nesting kf8 and mobi in the one and only main stylesheet. Guess it depends on how much complex formatting there is. Your method seems cleaner - you know what is in what. Do you comment out the KF8 and Mobi for your ePubs or just leave them in? They should be ignored, of course, but one always wonders what little glitches can arise.