In a thread over
here, Kovid said:
Quote:
Originally Posted by kovidgoyal
When you view an EPUB file using calibre's viewer it will insert that file into the EPUB. Apparently, the good folks at Apple have even less of a clue as to how to validate EPUB files, so they complain about it. If you want to use the calibre viewer to check your EPUB files before submission, I suggest doing it on a copy of the EPUB.
|
Is it possible for Calibre's viewer to... not do that?
Here's why I ask. I'm on Mac, and I've been looking for a while for an Epub reader that is
just a reader -- that is, one that lets me double-click on a book in my filesystem, open it, read it, close it, and not deal with additional content management overhead, not copy the file to its own special little DB, etc etc etc. The closest was FbReader, which I'm not happy with on Mac. So far I've been using BibTeX+BibDesk to manage my files and metadata (for citation purposes), plus Calibre for its Stanza integration (at which it excels, but which I run on a different computer, duplicating a subset of my library), but my best workaround for reading the Epub was to install the Firefox Epubreader plugin and just let it make its own copy of the book.
I have just realized that invoking Calibre's ebook-viewer from the command line is almost exactly what I want. Simple, reads the file in place, doesn't force me to navigate through another library structure. Not what I'd call lightweight (70+ megs of RAM to display a 750K Epub?), but acceptable. Only problem is that it unexpectedly alters the Epub file I opened. Which I really don't want. If a
reading program is going to change a
static document, I really want to request that behavior, not have it happen for me. As far as the ebook-viewer program is concerned, I'd be totally happy if that request was the act of explicitly clicking on the "add bookmark" button. But if I don't do that, I don't want the program going in and putting a bookmark file into my otherwise clean Epub files.
I discovered this when I tested ebook-viewer earlier today, and noticed it changed the timestamp of the file I viewed. Then I made two copies of another Epub file, viewed one, unzipped them and compared the contents. I checked the FAQ and docs on the website, but didn't see anything. Google revealed only the thread from which I took the above quote, plus another one
here where nothing is resolved.
Upon closer examination, I see that the bookmark file stores where I last closed the book. As far as I'm concerned, this is even less desirable behavior, though I see now why it is the default behavior. Is it possible to add a command-line option to disable bookmark writing? Is this a change that might be considered if I raise a ticket? What if I were to contribute a patch? Should I just wrap ebook-viewer in a script that 'chmod 444's the file before and 'chmod 644's after?