View Single Post
Old 04-25-2014, 02:34 PM   #712
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: 28,621
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
OK. The two small changes I've included have nothing to do with the kindleunpack.py file, so everything will be relative to the current (v064) version posted.

The patch I've attached affects the mobi_k8resc.py file and the mobi.opf.py file. Should be able to patch with the typical "patch -p1 < KindleUnpack.patch" method (starting from just outside the 'lib' directory of the source).

The change to mobi_k8resc.py simply eliminates the 'properties="cover-image"' attribute/value from the cover image's <item> entry in the <manifest> section of the OPF file. "properties" is not a valid/recognized attribute for the 'item' tag in ePub 2. An ePub won't validate with it in there.

The change to mobi_opf.py has to do with the guide section of the OPF file. I may have given you this patch before. The current version is putting the entire title of the ebook (from the EXTH) into the "title" attribute of the cover page's <reference/> entry in the <guide> section. That may not ever cause an issue, but it's typically just a static value of "Cover" (although it doesn't really matter what's there). It just doesn't make sense to me to put the entire title of the book there. *shrugs*

Quote:
Originally Posted by KevinH View Post
As far as I know, we are still waiting to hear back confirmation from the original bug reporter that the fix works with all of his test cases. But I am not sure they actually will report back.
For what it's worth, I had books that were behaving in exactly the same manner (getting the same error) as the bug reporter's and the proposed fixes to kindleunpack.py worked with those problem books.
Attached Files
File Type: txt KindleUnpack.patch.txt (935 Bytes, 207 views)

Last edited by DiapDealer; 04-25-2014 at 02:54 PM.
DiapDealer is offline   Reply With Quote