Quote:
Originally Posted by KevinH
Hi,
Which version of Sigil are you using? Is it repeatable or random? Can you provide a sample document and walk me through the steps to recreate this?
KevinH
|
Hi Kevin,
I am using 8.4 and the problem appears to be random, but I'll bet you that there is more than one assignable cause.
The problem happens most often when:
I import a new stylesheet for an epub that already has a stylesheet associated with it; the name of the new stylesheet does not seem to make a difference. If I'm starting an epub from scratch, I am less likely to run into the problem.Saving the new stylesheet, even with an extra space or null class, does not always solve the problem either.Lost css almost always occurs if you link the new stylesheet first and subsequently make a change in the metadata editor, though the css won't "blank" until exit.
I originally thought the bug was related to how the exit conditions were set, though not necessarily how those conditions impact content.opf *, but changing the clean source settings didn't have a noticeable impact over time. I tested different settings for about 2 weeks, and finally went back to clean on open and save, using html tiddy.
The single best indicator that my css will blank is how Sigil behaves when I link a stylesheet. The problem will
always occur if Sigil visibly jumps from file to file when linking is executed, but almost never occurs when the html files are read as a block. It gets even stranger when one looks at the individual links after "file jumping", because they are written correctly, yet on exit from Sigil the stylesheets "blank".
I'll send you a sample the next time the problem happens, but video of a workflow would probably be better.
Thanks,
Pete
---
* If it were a problem with how the opf was written, simply dragging, dropping, and saving new copies of the sylesheets using Winzip would not correct the problem.