Quote:
Originally Posted by DiapDealer
I tried saving the epub myself to see if it made a difference in my testing--and it didn't. The only question is where did you save the epub to before? Hopefully not in the repository (not that it should really matter).
I clearly need to give the instructions a bit of TLC. For changes that are simple enough to finish in one quick session, there really is no need to save the epub when working on changes to the guide. The only real reason to save would be because you're not done editing, but you need to close Sigil or the epub and come back to it later.
It's true that saving an epub in Sigil will cause Mend to correct things it thinks are wrong (if the default preferences for Mend on Open/Save are being used). But in my testing, the user guide's source was already in a "state of grace" so Mend on Save didn't result in any changes.
|
The saves of the epub that I made were to Desktop - certainly NOT to the repo. And, now you mentioned it, the Preferences were set for Mend on Open & Save. In each of the three attempts, the few edits I made were all done in a single, short session.
I would have expected my fork and its clone to have been in your "state of grace" when I started, on all three attempts (each with fresh, clean forks and clones). So why did the save to a temp.epub cause so many changes to files which I didn't even open let alone edit? Maybe, the source was not in its "state of grace"?
The second attempt was an improvement on the first, but still the fresh-start fork should have been in that "state of grace".
The only difference I made on the third go was that I saved a temp epub copy, AFTER the FolderOut operation was completed.
The lesson I'm drawing from this is that the order of events seems to matter for reasons I don't understand. But pragmatism shall prevail in the future unless further discoveries turn up.
