View Single Post
Old 03-01-2012, 01:05 PM   #9
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 10,771
Karma: 11200002
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2
Quote:
Originally Posted by taskforsome View Post
Thanks again.

A last question. Which are the most common differences/elements in order to be considered in MOBI format? I mean, like the trouble with images...
The other problem you will likely have is with CSS statements. Mobi format does not support CSS at all, nada. The conversion programs will attempt to convert some CSS into something that mobi will understand but it can be spotty and the results may not look like what you expected. KindleGen tends to be better at converting CSS than is MobiPocket Creator.

The ePub specific toc file will be used by KindleGen to create the chapter marks on the progress bar but not to create the Mobi specific TOC. It will need to be created separately. MobiPocket Creator can make this by identifying the rule used to create it such as all h1, h2 headers.
DaleDe is offline   Reply With Quote