Quote:
Originally Posted by nynaevelan
Just to add to this conversation, the only collection which shows up in the collections column in the device view on my k2, is the collection which I created on the kindle. I used to be able to see them also, but I do not know when they stopped showing up as I rarely look at that info but I do remember it was never 100%.
|
A post by Kovid in another plugin thread may have just inadvertently identified the cause of this issue. Thanks to your collections file the link was obvious.
It seems that Calibre writes the Calibre UUID of a Mobi book into the same field that Amazon stores its ASIN number (to allow syncing to Amazon). When my plugin reads mobi files it uses the code found in that field as the code to put in the collection list. If no code is found it creates a code based on the pathname. Since there is a code in the field, the plugin uses it - not knowing its not an Amazon ASIN identifier - it should really ignore it and just generate the code from the path name.
The Kindle appears to know that the code is not really an ASIN number, ignores it and calculates a new code based on the pathname. So it shows books in collections ok. Since Calibre only knows how to generate the code from the pathname it is looking for that pathname code and not the UUID code.
I just need to modify the plugin to skip the code if its not an ASIN code. The question is whether Amazon ASIN numbers are a fixed format/length. If so I can ignore anything not matching that format. Or if Calibre UUID is a fixed format I can include everything but the UUID type codes. Its not clear if anyone else uses the same asin field besides Amazon and Calibre. I wonder if other Mobi book creating tools populate it.