View Single Post
Old 01-15-2012, 04:15 PM   #2
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,386
Karma: 203720150
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I've actually been having better results converting epubs to mobis with the new version of kindlegen.

I don't think the new guide is getting ahead of itself, but granted... I've only tried using the @Import method from the guide, so I can use two completely separate css files—one for MOBI and one for KF8.

I just have a blank stylesheet except for:
Code:
@import url(../Styles/mobi7.css) amzn-mobi;
@import url(../Styles/kf8.css) amzn-kf8;
That barebones stylesheet is included in every xhtml file in the epub. Then I have two different stylesheets (named mobi7.css and kf8.css) where all the nitty gritty happens.

You can also do a:
Code:
@import url(../Styles/common.css);
@import url(../Styles/mobi7.css) amzn-mobi;
@import url(../Styles/kf8.css) amzn-kf8;
Where all the common stuff is one css file and only the special styling circumstances need to go in the two format-dependent css files.
DiapDealer is online now   Reply With Quote