FYI:
Early on, when computers were quite slow, Sigil took a long time to import ebooks. To get around that the original author of Sigil cached pages and used placeholders on disk (so that the time to actually write the file to disk could be saved during import).
So in older versions of Sigil, there were cases were files were imported (like Fonts) but they were not actually written into the working folder because you can't edit them and so a placeholder on disk was used until someone actually did a save.
So it is entirely plausible that editing a file (especially in older version of Sigil) might force a cached document to be saved to disk and thereby replace an empty placeholder.
I have tried to track all of those down and fix them since plugins needed all files written to disk (even before the first save). In theory it could still exist but I have never seen that bug myself. But what you are talking about is not inconsistent with how older Sigil (and possibly current Sigil?) worked.
KevinH
Quote:
Originally Posted by Turtle91
Pretty sure they aren't the culprit. AFAIK plugins weren't available on 7.xx, which is where I've seen the problem. I have NOT seen it (yet) on 8.4 - after 3 books without using my workaround.
I don't think it would be a 3rd party issue...although one never knows... why would adding a space to the CSS file prevent it from blanking? Is there some algorithm that changes an imported file's status once a change has been made...would said status change put the file in a category where Sigil would have to save all the data - where Sigil could ignore a file that didn't change?
|