Quote:
Originally Posted by jhowell
That is not surprising. The files you replaced contain a cache the annotations, but the master copy is still on Amazon's server. There is no way to force those cached annotations to be sent to the server. Only newly generated annotations are sent back to Amazon.
|
Ahh that is really useful to understand.
I presume, that is the case with any metadata file sideloaded to the kindle vs. being created on the device itself, right?
So it even if it could be done to generate a .azw3r/-f equivalent file for a .mobi book (.mbp, etc) then the corresponding annotations and highlights (sideloaded to the kindle) would not be uploaded to amazons servers unless they were created or edited on the kindle (or other kindle app or device). Is that correct?
Quote:
Originally Posted by jhowell
That is also to be expected. Annotations locate the precise point in the book using a "position" number that is based on the exact HTML content of the file produced by kindlegen. The e-book source file recovered via kindleunpack will not match the original source file exactly, leading to this sort of minor discrepancy.
|
Okay. Thanks a lot for the clarification! So, whenever a book is converted from one format to another it will generate these kind of discrepancies…