Consider adding opt-in support for parsing XML 1.1 about parse-xml HOT 3 CLOSED

Hmm. Based on my understanding of Section 2.2 of XML 1.0 5th ed., control characters are invalid in XML documents even when represented by a character reference.

Just in case I misinterpreted the spec, I tried parsing <a>hello&#x7;</a> with libxml2. It produced a parser error:

parser error : xmlParseCharRef: invalid xmlChar value 7
<a>hello&#x7;</a>
             ^

I'd prefer not to relax this check, even via an option, since it seems like doing so would result in a parser that consumes invalid documents, and my goal with parse-xml is to conform to the spec as closely as is practical (minus the unsafe parts).

Of course, you should feel free to maintain this change yourself in a fork if it would be useful to you!

from parse-xml.

Thank you for your feedback. It seems that my files do conform to XML 1.1, as Section 2.2. of XML 1.1 does expand the char class to allow these additional control characters. My understanding is that XML 1.1 is not very common or widely implemented, so I'll just try some changes in my fork.

Thanks again.

from parse-xml.

Ah, interesting.

My reason for not implementing an XML 1.1 parser is basically that I came across this old excerpt from the book Effective XML, which pretty strongly recommends not bothering with XML 1.1:

Everything you need to know about XML 1.1 can be summed up in two rules:

1. Don't use it.

2. (For experts only) If you speak Mongolian, Yi, Cambodian, Amharic, Dhivehi, Burmese or a very few other languages and you want to write your markup (not your text but your markup) in these languages, then you can set the version attribute of the XML declaration to 1.1. Otherwise, refer to rule 1.

But I'm not completely opposed to the idea of adding XML 1.1 parsing capability as an opt-in feature via the <?xml> directive and/or a runtime option, if it's something that would actually be useful and if it could be done without adding significant complexity or code weight.

from parse-xml.