View Single Post
Old 04-27-2012, 10:15 AM   #359
jhowell
Groupie
jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.jhowell never is beset by a damp, drizzly November in his or her soul.
 
jhowell's Avatar
 
Posts: 195
Karma: 59999
Join Date: Nov 2011
Location: Florida
Device: iPad 2, Kinde PW II
I’m not sure what tool produced or manipulated it, but I recently came across a mobi7 file that contains several FONT sections with no data in them. This book is viewable in Calibre and Amazon applications, but caused mobi-unpack to fail. I mention this as a “heads up” in case others come across this sort of malformed file.

FYI: The error occurs in the struct.unpack_from call following elif type == "FONT" in mobi_unpack.py. I patched my copy to skip it if the data length is too short.
jhowell is offline   Reply With Quote