That is an old bug in the Sigil plugin quickparser.py code that doesn't handle comments without a space after the <!-- . It was fixed previously but the fix got lost somehow or never committed properly to master.
I will fix this for the next Sigil release. To temporarily work around it please add single space after the start of the comment "<!--" string.
Thank you for your bug report.
KevinH
Quote:
Originally Posted by AlanHK
I found a weird effect when I converted a file with some commented out code:
Original code:
After conversion:
It has deleted the comment close bracket and also the title of the commented out image link.
So the comment is not closed, the rest of the page disappears, and is invalid.
I would expect whatever I put inside a comment tag should just pass through any conversion.
A lesser annoyance: After the conversion finishes, it asks for a save location and defaults to the top level of "Documents and Settings" every time (I'm using Windows). So I have to click up and down to find the folder I'm working in. Next time it's the same. I would like an option to default save to the same folder as the source, and/or the same folder as used last time.
|