Quote:
Originally Posted by KevinH
You misunderstood. I am not saying that file modification dates in the epub are not useful. I am saying the way Sigil recreates the entire epub makes them useless to you.
Have you tried Sigil's internal git based Checkpoints/Compare toolbar and tools? It really will show you what has changed quite easily inside Sigil. Outside Sigil file hashing is the best way to detect changes in files if modification dates can not be trusted.
...
|
As a mention, I cannot overemphasize enough how much I hope someday, and how much it means to me (and maybe others). I'd think despite unzipping to a temp folder, archive dates could be preserved, and if edit state is tracked, perhaps just such files would have the date changed on save.
It may be a little while before I get to trying it myself; maybe I could figure it out with enough effort, yet maybe the change isn't do bad, if merely you thought too it to be important and were willing.
As for using checkpoints, as mentioned, I may just update metadata, restructure to Sigil Norm, compress files (typically outside w/external tool), edit CSS, subset fonts, edit TOC, or other, or some combination of all or a few or one. E.g., for commercial epubs, I may merely make a few changes or substantially change. It would be difficult to checkpoint every EPUB. Imagine doing such for one's entire calibre library? And if someday Sigil is no longer the tool of choice? Years later, if I wish to know if I've compressed images or what is the possible (corrected) revision of some purchased EPUB (dates is one indicator), or have some other question, much can be determined, at least enough for me for various reasons, that such dates are so significant. You yourself seemed to have suggested mod dates are too important.
