How to access all identifier when writing mobi files?

[siebert]

Originally Posted by kovidgoyal

When you are dealing with a closed and opaque system like Amazon, it's best not to make assumptions about how "unique" something is and what the ramifications of a collision would be. So no, I am not going to accept a patch that uses the asin instead of a uuid.

I would like to get some facts from you instead of just FUD.

That Amazon syncs the position between mobi files containing a uuid in the ASIN field is also certainly not intended by Amazon, but we know that it (currently) works.

Using a valid ASIN is also known to work and has the additional advantage that Amazon supplies and displays a correct cover.

If you really think that giving a calibre converted mobi the same ASIN as the official Kindle ebook is harmful, it would be possible to use only ISBN-10 values of the paperback or hardcover versions as ASIN, which will never be used by Amazon for their Kindle version but still gives a matching cover.

There are already scripts to automatically find and include the correct ASIN for a mobipocket file (see https://www.mobileread.com/forums/sho...d.php?t=117645) which works fine for lots of people. I started to write my own Python version but came to the conclusion that calibre already has all the information needed and can write the ASIN value, so with a few additional lines of code calibre can be modified to do "the right thing".

Ciao,
Steffen

[kovidgoyal]

> /dev/null