View Single Post
Old 07-03-2015, 01:52 PM   #1167
R. Scot Johns
Author/Illustrator
R. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with othersR. Scot Johns plays well with others
 
R. Scot Johns's Avatar
 
Posts: 14
Karma: 2952
Join Date: Mar 2012
Location: Boise, ID
Device: iPad 2 & 3, Kindle Paperwhite, Kindle Fire 1 & 2, HD7 & HD8.9, RazrMax
Quote:
Originally Posted by DiapDealer View Post
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.
Let me clarify this a bit. What I did was unpack the .azw3 that was unpacked from the original mobi file. So it's a second unpacking, as it were. If you unpack and split the source mobi, then unpack the resulting split azw3, you get a mobi7 folder full of images (but nothing else) as well as all the normal content in the mobi8 folder, the combined size of which is larger than the azw3 source, even discounting the recreated epub3.

Therefore, the unpack process in this case is actually creating a mobi7 component from the split KF8 file, if, as you say, it is not present in the split azw3 file. However, I believe it actually is present in the azw3, at least as a housing for the compressed images that are sent to non-HD devices.

The reasoning for this is due to some confusion on my part over the function of the "Use HD Images" option, and its resulting output. Here is what I'm seeing when unpacking the split azw3 with/without this option ticked:

Use HD Images:
* BOTH mobi7 and mobi8 folders contain HD images

Do NOT use HD Images:
* NEITHER mobi7 or mobi8 folder contain HD images (i.e. both have compressed jpegs)
* HDImages folder created containing HD images

In neither of these cases do the resulting files equal the input file size (even discounting the produced epub3 source file, the size of which is relative to the images being used).

However, upon further inspection/calculation, the combination of one file from each iteration (i.e. one HD image folder plus one non-HD image folder) does equal almost exactly the input file size. This leads me to believe that both are present in the source azw3, but are not being extracted accurately (that is, with one folder containing each version of the images). Only when unticking "Use HD Images" do you get both, but in this case you actually get two sets of compressed jpegs as well as the original size images in their separate folder. This is where my confusion lay.

As my understand has been that the purpose of KU is to ascertain what exactly is occurring in the source conversion, my natural presumption was that the unpacked content reflected what was actually in that file (with the caveats for the reproduced epub structure files). Perhaps I was expecting more fidelity than is intended.

It is ultimately not important at this point, other than as an academic exercise, which is always useful to further understanding in my experience. Otherwise, I walking around looking like this: which is not uncommon.

Thanks for bearing with me as I muddle through this. Mostly I could have worked it out on my own, but sometimes it's easier just to ask.
R. Scot Johns is offline   Reply With Quote