Another possibly irrelevant issue:
Beautify also changes <?xml version="1.0" encoding="utf-8"
standalone="no"?> into <?xml version='1.0' encoding='utf-8'?>
And another possible suggestion, although it's a matter of preferences.
Imagine this
Code:
<p>Example paragraph with <i>italics</i> inside</p>
And then because of an editing error you forget the closing </i>.
In this situation:
- Sigil gives you an error in the preview saying "html error in line whatever" or something similar. And it actually stops the file rendering in that paragraph.
- Calibre silently "fixes" it with a greedy approach (the only one it can actually have). It converts the former paragraph into
Code:
<p>Example paragraph with <i>italics inside</i></p>
without any warning.
Well I really hate intelligent software doing what it thinks it's right on its own... I prefer being told that I've got some kind of trouble, but being forced to solve it myself.
Nevertheless I suppose that a fully "automatic and smart" behaviour is always preferable in a fully automated tool like, as example, the Calibre file format converter. But I think that an
advanced tweaker, like this Sigilish editor is intended to be, shouldn't behave in the same way. The user should retain full control all the time.
But as I started the post saying it's just a preference issue. Maybe a lot of people will prefer the current automated behaviour. It's up to you changing it or not, each solution has its own advantages and disadvantages.