View Single Post
Old 09-04-2012, 04:09 PM   #17
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,652
Karma: 205022288
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by SusanM View Post
Both nested and external media queries work for me. I was wondering about whether commenting out for epub works well or whether best to use a separate file to convert through KindleGen. You haven't had a problems with Amazon with the epub.css?
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.

Last edited by DiapDealer; 09-04-2012 at 04:19 PM.
DiapDealer is online now   Reply With Quote