View Single Post
Old 09-24-2014, 06:08 AM   #10
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,786
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by PeterT View Post
Maybe the point I am not getting is that you DO WANT the last read location stored, just not in the ePub itself?
Not often I speak for others, but it's pretty clear that's what Jon wants - but the question is, where to put the last read position.

If it were written to the metadata.opf file then that would change the raison d'être for those files, the means to reconstruct metadata.db. It would become a sidecar file that would need to follow the epub wherever it roams and it would have to have a unique name because as things stand they're all metadata.opf.

If one was willing to forgo having last read position follow the epub when and where ever it roamed then perhaps one could put the last read position (calibre_bookmarks->calibre_current_page_bookmark) with the viewer_open_history in viewer.json in calibre's config data.

I think you'd need a 3 choice setting for Save last read position - don't save, save with recently read, and save in the book.

BR

Last edited by BetterRed; 09-24-2014 at 08:29 AM.
BetterRed is offline   Reply With Quote