Quote:
Originally Posted by KevinH
Prettify changes whitespace in an attempt to cleanly indent html code to make it more readable by humans. I typically only use this if I am starting from code that is horrible.
Mend tries to make no whitespace changes and does the absolute minimum to fix broken html.
I personally use mend on open only and that is because gumbo will fix the code so that it is parseable to update links and things when an epub is first opened anyway.
CSS setting is personal preference since epub2 is somewhere between those two CSS specs.
Tidy is no longer part of Sigil because it often ate text.
|
Thanks Kevin. I was just testing the Mend vs Mend & Prettify. I've always used the Mend and prettify instead of the Mend. I like it that Mend/Prettify removes the white spaces and straightens things out. But you say Mend does the absolute minimum to fix broken code. Is that a good thing? By using Mend/Prettify am I at a disadvantage to using just Mend?
(And I don't think I have a lot of broken code. I'm just doing my own stuff. Stuff that I write and then turn into an epub.)
You wrote:
Quote:
|
I personally use mend on open only and that is because gumbo will fix the code so that it is parseable to update links and things when an epub is first opened anyway.
|
The above is kind of over my head. What is gumbo? The way you wrote it it sounds like Mend
and gumbo are both fixing the code.
Is there any disadvantage to the way I have it (having Mend on Open and Save)?
And I googled and CSS 3 has a bunch of new stuff. But is my CSS going to need anything more than the CSS 2.1?