'utf8' codec can't decode byte 0xb1 in position 18: invalid start byte

[oj829]

Originally Posted by kovidgoyal

If 0.9.6 did not work with that file open a bug report and attach the file, I'd be interested in taking a look at it.

It DID work in calibre 0.9.6 after 7Zip got rid of the corrupted filename in the epub.

You still want me to file?

[oj829]

Originally Posted by kovidgoyal

If 0.9.6 did not work with that file open a bug report and attach the file, I'd be interested in taking a look at it.

Okay -- shoulda looked at the Tools first. It's been a while since the Adobe-relevant plugin to my library situation was updated in Tools, but it is now at v0.1.9 (Tools 5.4, November 6 2012) versus v 0.1.7 (Tools 5.31, September).

I just updated the plugins from Tools 5.4, restarted book download process from scratch, and the book came into Calibre just fine, including the "Chapter 36" graphic which I lost when i implemented my crude "home brewed" solution (i.e. removing the offfending "corrupt" graphic file with 7Zip).

[KevinH]

Hi Kovid,

To workaround these issues, ePubFixer uses its own zipfile.py version called zipfilerugged.py which is simply the official zipfile.py file with this one change to explicitly catch the decode problem when garbage central directory filenames are used with the encoded as utf-8 flag (and they are garbage chars, not utf-16 as far as I can tell).

    def _decodeFilename(self):
        if self.flag_bits & 0x800:
            try:
                return self.filename.decode('utf-8')
            except:
	        return self.filename
        else:
            return self.filename

This prevents zipfilerugged.py from barfing out when simply trying to open the bad zip.

Then to fix the cases where central and local filenames differ (again because of garbage chars in some central directory filenames), ePubFixer uses the following code that imports the zipfilerugged.py

(see attached zipfix.py)

Your new approach of reading the entire zip by processing the local information only should be more robust and closer to what B&N is using but ePubFixer works too.

Hope this helps.

KevinH