Quote:
Originally Posted by johnnyb
I just checked all documents I've sent to my Kindle after updating to 3.3 and some, for no apparent reason, show "delete" instead of "remove". Wonder what makes them different, they show up in the archive and all (although they do not disappear after having been downloaded to the Kindle). I'll try a couple of things and then report back ;-)
UPDATE: It seems, some files were simply not working, had to convert them to epub and reconvert to mobi, don't know if a simple reconversion would have done the trick but I don't like the calibre mobi conversion... maybe someone can comment on that...
|
I still need to do some more tests, but it seems to be the case that if you send a .mobi file, Amazon will convert it to .azw, and they don't just change the file extension. I sent one that was 16.6MB and the .azw is only 5.9MB. But it is all there. The .mobi in this case was from my O'Reilly library. I think O'Reilly is using kindlegen, which includes a .zip with the original source files in the resulting file (the epub version is 9.6MB). Amazon strips the source files out when converting to .azw, hence the smaller size. They may also be putting some metadata in there with some UID (unique identifier) to facilitate the syncing etc.
I assume they do the same with .prc or .azw files. So the file that gets put into the PD library is not the same as what you sent.
So what about the ones that show 'delete'? anything special about them?
Calibre adds (or at least used to) a random 'ASIN' to the mobi files it creates as a hack to coerce synching. There's an option to turn this off (in MOBI output preferences). I'm not sure what 'output' applies to altogether (if I import, then Send, does it do anything other than change file name?), but at least I will be turning the 'Enable sharing' option on so it doesn't do this any more (and maybe this default will/has changed in future calibre release, I'm still on 0.8.19). Anyway, might be something to keep an eye on.