Quote:
Originally Posted by leftright
I edited/converted a book in PC-Calibre and embedded the metadata.
Connected CC-Tablet to PC-Calibre wirelessly, It synced and updated metadata.
The edited book wasn't sent/synchronised across, why ?.
|
Probably because you haven't enabled the "Sync Newer Book Files" option in CC. If that option is not checked, CC only syncs metadata.
Quote:
I deleted the book in CC-Tablet, resent the book from PC-Calibre.
when opening book from within CC, FBReader showed old book.
I deleted the old book from within FBReader
Resent boook from PC-Calibre and now the new version of the book opens in FBReader.
Is it necessary to go through all those steps to ensure that a book edited with PC-Calibre is correctly synchronised in CC AND FBReader ?.
|
If you check the option described above, CC will fetch changed books and store them wherever you have indicated in CC's settings.
I installed FBReader to test. The steps I took:
- Opened a book in FBReader
- Closed FBReader
- Changed the book in calibre
- Connected CC as a wireless device choosing "Sync books". The new file was sent to CC. I verified that the timestamp of the file changed using a file manager.
- Opened the book in FBReader from CC. The old text was still there.
- Opened the book in FBReader from a file manager. The old text was still there, demonstrating that it isn't a CC problem.
- Opened the book in Moon+ from CC. The new text was there.
- Opened some other book in FBReader then opened the original book. The new text was there.
Conclusion: apparently FBReader keeps a secret copy of the last book being read and does not check the timestamp of the file. There isn't much that CC can do about this.
The workarounds I see:
- Open a different book in FBReader then reopen the desired book. This process seems to replace the secret copy.
- Delete the book in FBReader before connecting CC. CC + calibre will resend the book if you have the option set and choose Connect/Sync books. IMO this isn't a good workaround.
- Use a reader app that doesn't have this problem.
There might be a setting in FBReader that affects this, but if so it isn't obvious.