Fix two typos
Potential to end up looping until you run off the edge of the array and hit an IndexError traceback, isn't there? Correct, but do note that there is a try in _locate_metadata that would catch this or other forms of file corruption. I'm not completely convinced that returning an incorrect value is better than throwing an exception in the case of corrupt files, although if the purpose of the code had been to validate KFX files a better exception message had certainly been in order. :-) nit: "Unpexpected"...
@ferd617 As it says in that post, you can't download the files directly from Amazon, but you can send them to a Kindle or Android device, and then just transfer them from there. My code explicitly recognizes the file layout on eInk Kindle and can access it directly when mounting the Kindle as a mass storage device. You can also use the Calibre plugin to convert it you a kfx-zip if you like, since that format is also recognized. If you transfer the book to a black&white Kindle and get the files from...
I added one more commit to make searching for the metadata container more automatic.
Make KFX archive handler better at finding the metadata
Support for Kindle Format 10 (KFX)
add support for Kindle Format 10 (KFX)
Add support for MobiPicket format (i.e. Kindle)