Isn't there an unwritten law prohibiting document viewers changing the documents they open?
If there is, ebook-viewer, part of calibre, doesn't respect it:
diff -r m/META-INF/calibre_bookmarks.txt m1/META-INF/calibre_bookmarks.txt 1c1 < calibre_current_page_bookmark^7# *:eq(0) > *:eq(1) > *:eq(0) > *:eq(4) > *:eq(6) |0.19047619047619047 ---
calibre_current_page_bookmark^15# *:eq(0) > *:eq(1) > *:eq(0) > *:eq(8) > *:eq(43) |0.3619791666666667
The directories that I compared contain unzipped versions of the same epub file before and after an invocation of ebook-viewer. Probably calibre_bookmarks.txt was put in the epub file by ebok-viewer in the first place.
Now one could say, that this is harmless, because it doesn't change the way the epub file will appear in any reader. But it changes filesize and timestamp, enough to make backup software notice.
Hopefully, unchecking the "Remember the current page when quitting" in the Preferences is a workaround, but even then, it's just a workaround. ebook-viewer is welcome to have its own little database of bookmarks, but shouldn't annotate my books.
Andras
On Fri, 2012-05-11 at 14:11 +0200, Andras Simon wrote:
Isn't there an unwritten law prohibiting document viewers changing the documents they open?
If there is, ebook-viewer, part of calibre, doesn't respect it:
diff -r m/META-INF/calibre_bookmarks.txt m1/META-INF/calibre_bookmarks.txt 1c1 < calibre_current_page_bookmark^7# *:eq(0) > *:eq(1) > *:eq(0) >
*:eq(4) > *:eq(6) |0.19047619047619047
calibre_current_page_bookmark^15# *:eq(0) > *:eq(1) > *:eq(0) > *:eq(8) > *:eq(43) |0.3619791666666667
The directories that I compared contain unzipped versions of the same epub file before and after an invocation of ebook-viewer. Probably calibre_bookmarks.txt was put in the epub file by ebok-viewer in the first place.
Now one could say, that this is harmless, because it doesn't change the way the epub file will appear in any reader. But it changes filesize and timestamp, enough to make backup software notice.
Hopefully, unchecking the "Remember the current page when quitting" in the Preferences is a workaround, but even then, it's just a workaround. ebook-viewer is welcome to have its own little database of bookmarks, but shouldn't annotate my books.
This would best be reported to Calibre's upstream bug tracker: https://bugs.launchpad.net/calibre
They're a very responsive upstream, so I imagine you'll get a prompt answer.
2012/5/11, Stephen Gallagher sgallagh@redhat.com:
This would best be reported to Calibre's upstream bug tracker: https://bugs.launchpad.net/calibre
They're a very responsive upstream, so I imagine you'll get a prompt answer.
Thanks, I'll try this next, but first I'm following the official way and reported it as https://bugzilla.redhat.com/show_bug.cgi?id=821135
Andras
Stephen Gallagher wrote:
On Fri, 2012-05-11 at 14:11 +0200, Andras Simon wrote:
Isn't there an unwritten law prohibiting document viewers changing the documents they open?
If there is, ebook-viewer, part of calibre, doesn't respect it:
diff -r m/META-INF/calibre_bookmarks.txt m1/META-INF/calibre_bookmarks.txt 1c1 < calibre_current_page_bookmark^7# *:eq(0)> *:eq(1)> *:eq(0)>
*:eq(4)> *:eq(6) |0.19047619047619047
calibre_current_page_bookmark^15# *:eq(0)> *:eq(1)> *:eq(0)> *:eq(8)> *:eq(43) |0.3619791666666667
The directories that I compared contain unzipped versions of the same epub file before and after an invocation of ebook-viewer. Probably calibre_bookmarks.txt was put in the epub file by ebok-viewer in the first place.
Now one could say, that this is harmless, because it doesn't change the way the epub file will appear in any reader. But it changes filesize and timestamp, enough to make backup software notice.
Hopefully, unchecking the "Remember the current page when quitting" in the Preferences is a workaround, but even then, it's just a workaround. ebook-viewer is welcome to have its own little database of bookmarks, but shouldn't annotate my books.
This would best be reported to Calibre's upstream bug tracker: https://bugs.launchpad.net/calibre
They're a very responsive upstream, so I imagine you'll get a prompt answer.
I can see value in having the bookmarks be a separate thing, it allows multiple readers against a single document, which might be shared in a business environment, or even read-only. Being able to have a single original document and let everyone have their own personal current page and bookmarks and possibly annotation, would be a good thing. Unfortunately that sounds like a fairly major change to the existing behavior, so it may not be practical.
On 05/12/2012 03:08 PM, Bill Davidsen wrote:
I can see value in having the bookmarks be a separate thing, it allows multiple readers against a single document, which might be shared in a business environment, or even read-only. Being able to have a single original document and let everyone have their own personal current page and bookmarks and possibly annotation, would be a good thing. Unfortunately that sounds like a fairly major change to the existing behavior, so it may not be practical.
That approach is also used by okular.
~/.kde/share/apps/okular ~/.kde/share/apps/okular/docdata
Modifications of the original files is an ugly idea, but I have to admit that it may have looked reasonable in a single-user mobile environment (copy the book -> copy also the related viewing info).
Nonetheless one thing is content and one thing is viewer state; in fact they happen to go in the same file, but the "file" is actually a zip container.