Quote:
Originally Posted by DiapDealer
We dont need "workarounds." We need step by step instructions to reproduce the bug, so that it can be fixed. If you haven't had an issue since you started using the workaround, how can you be sure the issue still exists?
|
Quite right. I was simply stating that I have had this problem for quite some time. I have not been able to track it down to a single step that causes it...or I would have reported it as a bug...and I had tried multiple times to reproduce it intentionally. You are also quite right that I can't be sure it's not still happening because it's fixed...I do know it doesn't happen after I started my workaround. I was hoping by bringing it up that someone more familiar with the code would have a
moment when I mentioned how I workaround it...
My methodology is to clean all the goop out of the html files...I know what's in my standard style sheet so I just put the codes into the html. After all that is complete I "add existing files" and put both my styles.css and sgc-toc.css in at the same time (multi-select). Both of these files have passed validation numerous times.
After that, I select all the html files and link them as a group to styles.css. This is where the "jumping files" mentioned before comes in. Sigil appears to process each html file (I assume adding the link tags) rapidly. Depending on how many things I have running in the background this might be slow enough to see the actual pages "flipping" by.
The css sheets import fine. I've never had it import a blank sheet. All the code is present.
I then will add any additional formatting to styles.css needed for that particular book.
I have not created the html toc yet, so there is nothing linked to sgc-toc.css. Somewhere in that process....sometimes.... I would check the sgc-toc.css file and find it blank...even though it imported properly. I USUALLY do not find a problem with styles.css ...but have occasionally found it blank as well. I have deduced that the times I find them blank are when I haven't changed the css files after import...thus my workaround.
I then will run the "Generate Table of Contents", and then "Create HTML table of contents". It seems to link fine, as the html TOC follows the formatting I have in the sgc-toc.
SOMETIMES, I have gotten so far as being finished with a book...checked each page...including the css... hit save and closed sigil. I only realize the blanking css has hit when I go to read the book and there is no formatting. I then go back and open the epub and TaDa....blank css files.
Again...this doesn't happen if I add a space to the css file after importing it....
I hope this helps!
EDIT: FYI, I have not seen this since upgrading to 8.4, but I have been performing my workaround for awhile as a matter of habit. I will stop doing my workaround *shudder* and see if I can get it to reproduce.