|
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.
Yes, earlier in that export epub code you can see where the file info is built that is written to the epub. Storing the epub fileinfo values somehow on import, then checking for changes on writing them out with stored values if unchanged might work. So you would need to extend the Resource.cpp base class in some way to store that info into the resource for each file.
|