Quote:
Originally Posted by itimpi
I thought the other devices wrote a calibre.metadata file to the device to help with matching the files?
|
Yes, it does, except for the ipad (but glancing at the code it appears to do something else). However, that doesn't change the situation. If you send a book to a device, then change the title, the metadata on the device will differ from the library. Devices that use .calibre.metadata use a UUID (unique ID) to match books that have been detected as the same in the past. I don't know if the iPad driver does this, or even can do this.
Quote:
|
Since it would be normal for the process of writing to the device to update the metadata within the file that is being sent to the device, the file inside the Calibre library is quite likely to be different to the one on the device.
|
Yes. That is why checking if the book files are identical doesn't work.
Quote:
|
As it is working via iTunes, I am not sure if the iPad driver is working in that way? If not the details for deciding the 'on-device' status may be different, and it might be necessary to force the copy of the file inside the Calibre library to have its metadata updated before sending it to the iPad.
|
Not sure what you are saying, beyond not being sure about how the iPad driver works (and I join you on that). What I am sure of is that calibre matches books against the library using the metadata from the calibre DB, not the book in calibre's library. The question is whether the iPad driver writes a book with updated metadata to the iPad when the book is sent. Of course, there is also the question about whether DRM will get in the way.
GRiker is certainly the expert on the iPad. Believe him before you believe me.
