View Single Post
Old 02-09-2016, 06:07 PM   #40
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@DiapDealer: From a (very) quick glance at the plugin code, KindleGen doesn't really enter the equation, the plugin's using the dualmetafix python script to add a 12 character one from a cropped random uuid (I'm guessing to more closely match the length of a real ASIN) to the metadata of the KG output.

Since it's mobi header metadata, KU properly preserves that when splitting. So, all's well .

It's just that the option is disabled by default, and one may not be aware that trying to use such KF8 files directly will risk upsetting the Kindle's framework .

And while doing it by default makes sense for Calibre, I'd argue that @Doitsu's choice was the right one here? He documented most of the underlying issues fairly well, and even I had forgotten how deeply messy it could be, so ;p. (That, or it got 'worse' since FW 5.5.x. But I'm way too lazy to check on an older device ^^).

Last edited by NiLuJe; 02-09-2016 at 06:13 PM.
NiLuJe is offline   Reply With Quote