View Single Post
Old 07-02-2012, 07:26 AM   #6
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: 27,548
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
You might want to also note that the <q> tag is only supported in the KF8 format (and only on the Kindle Fire) ... not the regular MOBI format.

The Amazon Kindle Publishing Guidlines gives you examples of several methods that can be used to specify separate CSS statements to tailor the MOBI portion in relation to the KF8 portion (and vice-versa). In short: starting with a validating ePub does not mean kindlegen will build from it, a MOBI/KF8 version that will be identical to the original ePub in every way. You have to learn what input Kindlegen will play nice with. The Amazon Kindle Publishing Guidelines is the place to start

Also, the "bloat" you're referring to is because the Kindlegen output contains the MOBI version (for devices that don't support KF8), the KF8 version, and the source used to create the file (in this case, the content of your ePub).

EDIT: and before you ask, no... any per/MB delivery fees that Amazon charges you is not based on the size of the file that Kindlegen produces. Only one version (MOBI/KF8) is ultimately delivered to the user based on their devices/app's capabilities. The size of the files sent to the user is the basis for that fee. Mobi_Unpack (post #5) is capable of splitting the KF8 portion of the combined file from the MOBI portion if you'd like to get an idea of the file sizes that an end-user would actually be seeing.

Last edited by DiapDealer; 07-02-2012 at 08:40 AM.
DiapDealer is online now   Reply With Quote