RFE: Improved whitespace treatment
"Leif Halvard Silli" <[email protected]>
| Newsgroups | gmane.editors.xxe.general |
|---|---|
| Message-ID | <[email protected]> |
I assume that the following issue is well known to the XXE developers as
well as to seasoned XXE users - steps to reproduce:
1. In XXE, create an HTML document with two non-empty subsequent <p>
elements as children of the <body> element.
2. Inspect the source code of the <body> element - it should look
something like this:
<p>Abc.</p><p>Def.</p>
(Then main thing being that XXE will automatically make sure there
is zero whitespace between "</p>" and "<p>".)
3. Now open or edit the document in another - XML-respecting - HTML
editor. (For instance BlueGriffon.)
4. Save the document. And then inspect the code - the line above has
almost guaranteed probably look something like this:
<p>Abc.</p>
<p>Def.</p>
(Whitespace has been added between "</p>" and "<p>".)
5. Reopen the HTML document XXE again.
6. XXE will now reformat the code - which is in principle is totally OK
(even if we know that many would prefer that it did not). However, even
if XXE reformats the code, it **will not remove** the whitespace between
"</p>" and "<p>". This is, in principle, also totally OK. However,
because XXE has a very specific way to render whitespace "in between
(certain) elements", this is still not really OK.
* EXPECTED RESULT: Visually, the document should look the same.
* ACTUAL RESULT: Visually, an empty line is drawn between the to <p>
elements.
* FEATURE REQUEST: Make sure that the document really does look the
same. This can be done EITHER by performing **more** code reformatting,
so that the "in between elements" whitespace is removed. Or by improving
the XML rendering. I will assume that it would be easier to improve the
reformatting of the code. In that regard, I would like to suggest an
(improved) XML code minifying process - some kind of "code import
process" which adapts the code to XXE's requirements.
Note, by the way, that in XXE it makes no difference whether one uses
the "Semantic viewer" or the "Browser viewer". If, at least, the Browser
viewer had been improved, then that would already be progress - it would
be a way to improve the rendering.
Note, also, that of course the current behavior does not affect the
semantics of the document. But it does hamper with the semantic view
... It sis irritating to have to see empty lines where there should be
none.
Leif Halvard Silli
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support