Quote:
Originally Posted by AlanRoberts
Okay. If the FBReader developers are interested in addressing this issue, they would need to capture UUID and something else (the <updated> tag?) when an eBook is downloaded, so they could reliably determine if a new title needed to be downloaded or an existing local title replaced with an updated download?
Thanks,
Alan
|
FWIW: The Calibre Companion wireless device driver handles these cases: book-on-device, changing metadata and changing books. Books are marked as on-device in calibre when CC connects. In the changing metadata case CC downloads the new metadata when it connects to calibre. In the updated book case one must set a CC option that causes CC+calibre to compare the modification time of the books in CC's library to calibre's library. Book "formats" (epub etc) newer in calibre are automatically downloaded to CC.
CC also uses the UUID to check for on-device in all three of its connections: wireless device, content server, and cloud.
One downside: CC replaces FBReader as the library manager. CC can use FBReader as the reading app.
If you have questions about CC, post them on
the CC forum.