illegal character not parsed as error

[arhebis]

While using Oxygen 13 I had a > character in the content of my xml which did not parse as error!

Unfortunately my client got totally pissed off about this ...

I think this is a serious problem. Do you have an explanation for this behaviour?

[adrian]

Hello,

It all depends on the context where the > character is being used. It's a common misconception that > is a strictly illegal character in XML. It is not, you can freely use it in text content, but it is illegal in some specific contexts.

From http://www.w3schools.com/xml/xml_syntax.asp , see Entity References:

Only the characters "<" and "&" are strictly illegal in XML. The greater than character is legal, but it is a good habit to replace it.

Do you have a sample XML file where you expected > to be reported as an error?
If you want to keep it private, you can send it to: support AT oxygenxml DOT com.

Regards,
Adrian

[arhebis]

Thanks for the reply Adrian, I will read the documentation you have posted.

Unfortunately I have discovered that the parse error was another - not reported by Oxygen 13:

I have an element with its children defined as a sequence:

<!ELEMENT ld-le ( le-begriff, le-eintrag ) >

in the actual xml file the structure was wrong:

<ld-le>
<le-eintrag>...content ...</le-eintrag>
<le-begriff>...cotent ...</le-begriff>
</ld-le>

and Oxygen reported the file as being valid! I used another parser (Eclipse) to parse the file and that one showed the error very clearly.

Thanks for your help,
Gabriela

[arhebis]

I posted this as a separate thread here:

http://www.oxygenxml.com/forum/topic8025.html