Thread: Generating mobi and KF8 parts of Kindle file from separate sources
View Single Post
Old 02-02-2012, 04:20 PM   #17
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,917
Karma: 6240958
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by DiapDealer View Post
I can get behind that scenario. It would be nice to know the ebook is simply not designed for your reader... rather than just receiving a random error message on your reader about; "not being able to open it; try deleting and re-downloading.." Even if it was only an option to have a one sentence "this ebook is not compatible with your device" old-mobi wrapper left behind by the splitter script.

On a related note... the old MOBI-only portion produced by the new splitter (now included with mobi_unpack) doesn't work with the Kindlepreviewer when emulating a Kindle Fire: "Open Error: error opening book.null" But the Kindle Fire Previewer handles other mobi-only files.
Hmm ... either the zero'd out sections are the culprit (but I don't really believe that) or some other information still exists that seems to convince the device that this is a mobi8 ebook when it is not.

There are other metadata elements than the element 121 BOUNDARY offset one that only seem to exist in the old mobi header of KF8s, so perhaps we should be removing them as well?

If I get a free moment over the weekend, I will run a few tests to see what if any info still exists that makes the device think it has a kf8 mobi when it does not.


KevinH
KevinH is offline   Reply With Quote