Amazon removed books from my Kindle

[DNSB]

Originally Posted by Sirtel

It may be a calibre issue, but it doesn't mean it's ok for Amazon to just delete random files from users' devices without any action on the user's part.
All I did was to replace EBOK with PDOC in check_fix.py in the plugin archive. I'm not sure that's a method everyone would want to use, as it replaces a feature (fix ASIN for Kindle Fire) with its opposite. Ideally the fix would be added as an additional feature, not replacing an existing feature, but I'm no coder and that would be beyond my scant skill set.

Perhaps replacing the check for EBOK in check_mobi.py with a check for PDOC?

[Sirtel]

Originally Posted by DNSB

Perhaps replacing the check for EBOK in check_mobi.py with a check for PDOC?

Yes, but there must also be a way to change it, not only check.

[DiapDealer]

In case anyone missed it the first time around:

https://github.com/SolaProject/mobi_...v-file#example

is a pure python, one-file module that can be used to check/change kindlebook metadata. Including EXTH[501].

It's also available to be installed with pip as mobi-header.

[Sirtel]

Originally Posted by DiapDealer

In case anyone missed it the first time around:

https://github.com/SolaProject/mobi_...v-file#example

is a pure python, one-file module that can be used to check/change kindlebook metadata. Including EXTH[501].

It's also available to be installed with pip as mobi-header.

But you can't use it with many files in bulk like the Quality Check plugin, or can you? That was what I was looking for. It would be awfully time-consuming to change hundreds or even thousands of files one by one.

[DiapDealer]

Originally Posted by Sirtel

But you can't use it with many files in bulk like the Quality Check plugin, or can you? That was what I was looking for. It would be awfully time-consuming to change hundreds or even thousands of files one by one.

Sure you can. Someone would have to put together a calibre user interface plugin that could be run on all Kindlebook formats of books selected in the library. But all the heavy lifting of editing the metadata would be done by the mobi_header module, so it shouldn't be a herculean task by any means.

[DNSB]

The check_fix.py change allows changing it. The change in check_mobi.py allows for choosing files that do not have PDOC as the cdetype.

Basically any instances in config.py, check_fix.py and check_mobi.py of EBOK (upper case) was changed to PDOC which made the dialogs make more sense.

[haertig]

Originally Posted by DNSB

Perhaps replacing the check for EBOK in check_mobi.py with a check for PDOC?

Since the length of the text string "EBOK" is the same length as the text string "PDOC", replacement could be as simple as this (on a Linux computer):

sed -e 's/EBOK/PDOC/' -i.backup 'filename.azw3'

The "sed" command on Linux works fine on binary files for things like this. But "sed" on Unix, Windows or some other OS may not handle binary files appropriately. A wise proverb: "An assumption is the first step towards a screw-up". So don't assume this will work on other OS'es, even if they have the "sed" command. You have been warned!

I do not know the structure of an AZW3 file, and it may be perfectly find to alter the length of text like this when doing a replacement. But I can't say that for sure, since I know nothing about AZW3 files and any checksums (or whatever) they may or may not contain.

If you are more daring and don't want to create a backup copy of the original file before editing, you can replace the "-i.backup" part of the command with simply "-i". This would be fine if you keep current and solid backups of your Calibre library.

You could write a simple "for loop" script around the "sed" command to find and cycle through all the azw3 files you want to modify.

You may want to add some bulletproofness to the script and make sure that "EBOK" only appears once in the file before you go modifying it. If it appears more than once, you only want to do the replacement on the appearance in the metadata part of the file (which is probably the first occurrence, but you'd have to verify that).

The way to check it the text string appears multiple times is:

strings 'filename.azw3' | grep EBOK | wc -l

Note that if you use "-i.backup" it will create a backup copy of every file before it gets modified. So you will need twice the amount of storage space to allow two copies of each file (at least until you remove the *.backup copies after you've determined all is well and good).