Quote:
Originally Posted by kovidgoyal
The MOBI output does not use the uuid as the uuid may not always exist.
|
But the mobi writer already looks for an existing uuid in the metadata and generates a new one only if there is no one in the metadata.
The question is, why is the epub uuid not available in the metadata? To me it looks like there is an uuid in the metadata (as it is also stored in the metadata.opf file) but one that calibre created instead of the one defined in the source epub.
Quote:
|
If you are planning to use the asin in the mobi header, I would urge against it as weird things are likely to happen if the MOBI file you use is different from the MOBI file associated with that ASIN on amazon's servers.
|
Could you elaborate on that? Currently I use mobi2mobi to replace the uuid with a valid ASIN or ISBN10 value to get the proper cover displayed in the Android/iOS Kindle app and I haven't noticed yet any issue, so what are the weird things you mention?
Ciao,
Steffen