Quote:
Originally Posted by R. Scot Johns
But why? What is the point in producing a mobi7 component on extract from the split azw3 if it's not in there in the first place? That creates an inaccurate representation of the source content.
|
It doesn't matter for your purposes. The content in the mobi7 folder does not affect the size or the content of your resulting azw3. And it's not "
producing a mobi7 component on extract from the split azw3." It's producing
all of the content from both the mobi7 portions of the original file and the kf8 portions of the original file. Selecting the 'Split' box doesn't change that. The split feature is a completely separate function from the unpacking process. Meaning that the split-out files are not created from the unpacked content (nor is the unpacked data being extracted from the split-out azw3/mobi). Unpacking and Splitting are completely independent of each other. The standalone KindleUnpack tool just doesn't give one the option to Split without also unpacking everything.
Quote:
|
My understanding, then, just to clarify, is that the split azw3 contains both sets of images for dual-format (low-res/hi-res for sending to HD/non-HD devices), but no actual mobi7 component, and that this is just created upon unpack/split by KU, drawing from (i.e. duplicating on extract) the low-res/compressed image files, thereby producing more actual content than was really in there in the first place (obviously, since the combined files are greater than the source).
|
Sort of (except for the "
more content than was really there in the first place" part) ... but since the unpacked content has absolutely no bearing on the two files (.mobi and .azw3) produced when splitting, it doesn't really matter.
Quite simply put: if all you're interested in is splitting to get a stand-alone AZW3, the rest of the extracted data is irrelevant.
Quote:
I just was unclear as to what exactly was happening, but you have answered that. So thanks. 
|
Glad to help.