Quote:
Originally Posted by exaltedwombat
The latest Sigil WILL save "bad" code. You get a warning when re-opening the file, but you aren't obliged to let either PrettyPrint or HTML Tidy mess with it. PP is unlikely to do any real harm. Tidy can, and HAS in my experience.
Some of us fought hard for this feature! It lets you save a session "as is" and come back to solving the problem later. Occasionally invaluable, though the arguments why we SHOULDN'T need to do this are easy to list :-)
|
Thanks Wombat. I think I'm getting this little by little. (I read up a bit on another thread about this too.) So it sounds to me like the new Sigil lets you save bad code, like you say "as is." I suppose it could be risky, letting pretty print or esp. HTML Tidy mess with bad code. So if you've got a doc with a lot of bad code that save "as is" would be really convenient. Now, for me, writing fiction with very little bad code, the save "as is" feature is not as valuable.
So, I'm going to get the new Sigil (7.1). So, how do I approach this (as a fiction writer with very little bad code)? I leave the Pretty Print on because it'll tip me off when I have the occasional bad code? (I'm just looking for a system.) Thanks.