Hussein, thank you for explaining the issue; I now understand that
instead of indenting (what I would expect from "pretty printing"), XXE
adds extra lines. I also understand this behavior can be disabled. I
still don't understand, however, why it is so hard for you to use
System.getProperty("line.separator") and generate platform-appropriate
line ending, as is best practices.
I also think that you seem to give up too easily. I am here as a
potential customer, telling you I really, really want to pay you for an
XML editor that can edit my XHTML5 files. But from the beginning of this
conversation, instead of working with me to see if there are ways to
tweak XXE to work the way I need it to, you have continued to insist
that XXE is not the editor for me. So I will take you at your word and
not bother you further about it.
It's too bad---I tried XXE years ago (when I didn't have money to pay
for it) and I believed and continue to believe that it needs just a few
small modifications here and there. (In fact both of the issues I raised
so far turn out to be configurable!! But again you keep insisting that
XXE won't work for me.) Besides the small programming tweaks, most of
all it would require customer support that actually had a desire to meet
customer needs. That seems to be the biggest element missing.
Good luck with your product.
Garret
On 11/29/2015 2:45 AM, Hussein Shafie wrote:
On 11/29/2015 12:51 AM, Garret Wilson wrote:
On 11/28/2015 3:26 PM, Gregg Reynolds wrote:
...
"Unfortunately XXE converted all my XHTML5 ends-of-line from CRLF to
LFLF!" isn't good enough; if XXE really did do such a silly thing I
want to know about it, but I need to know how to reproduce it.
Thanks Gregg! You are more professional than us. We should have
requested this from Garret. The problem was that we are 100% sure that
XXE does not replace CRLF by LFLF.
However Garret is right too in reporting a real, serious issue for his
use case. The CRLF-->LFLF mystery explained below.
Certainly! I'll be glad to help in any way!! You don't know how bad I'm
wanting a real XML editor.
This is easy to reproduce (XXE 6.5.0, Window 10 Pro 64-bit):
1. Select *File > Open...* and open the attached before.xhtml file,
which uses CRLF (U+000D U+000A) sequences for EOLs.
2. Select *File > Save As...* and save the file. It should be identical
to the attached after.xhtml file. Note that some CRLF sequences have
been replaced with LFLF (U+000A U+000A) --- for example on the first
<li>...</li> line. (Note after <meta/> as well.)
This is a short file for reproducing the issue. In a large XHTML5 file,
I get erroneous LFLF sequences all over the place.
Let me know what further information I can provide.
I opened the "before.xhtml" file you attached to your email in XXE and
attempted to reproduce the bug you have reported. I also used a text
editor to look at the "after.xhtml" file you attached to your email.
I've now understood what exactly is your problem. Thanks for sending
us these sample files!
My conclusions are:
1) There is a big, big misunderstanding here. What you call "replace
CRLF by LFLF" is simply how XXE *indents* (AKA *pretty-prints*) the
XHTML file.
By default, XXE adds open lines between child elements (<li>) when the
parent element (<ul>) may only contain elements (that is, not a mix of
text and elements like in a <p>). This makes the XML slightly easier
to read when you open it in a text editor.
These extra open lines can be easily suppressed by unchecking "Add
open lines" in the "Options|Preferences" dialog box, Save section.
See http://www.xmlmind.com/xmleditor/_distrib/doc/help/saveOptions.html
2) XXE is definitely not an XML editor for you, as it is designed to
take great liberties with how the XML is physically represented on disk.
Fox example, you have already noticed that by default, XXE suppresses
<?xml version="1.0" encoding="utf-8"?> when the <head> contains <meta
charset="utf-8" />. This way the XHTML5 file is processed by the web
browser as if it were HTML5.
This behavior can be changed too, but it's done the hard way by
customizing the stock XHTML5 configuration.
The stock <saveOptions> configuration element for XHTML5 documents is:
<cfg:saveOptions favorInteroperability="true"
omitXMLDeclaration="auto" />
See
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/saveOptions.html
3) You are right. XXE is not a "real XML editor". Years ago, we called
it "XMLmind XML Editor" simply because this makes it easier to find
using search engines. A more appropriate name would be "XMLmind
Structured Document Author". Structured documents happen to be always
stored in XML files, but the goal of XXE is definitely to allow
creating and editing structured documents, not XML files.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
