Hi Glenn, I personally agree with that, but I don't think the spec makes that clear.
If that's the intended behaviour, XMLVersionDetector shouldn't be trying to skip 0x85 or 0x2028 as it is right now, nor should the 1.1 document scanner treat any 0x85 or 0x2028 it encounters as an end-of-line in the XML declaration, so there's definitely a bug there. At 01:06 AM 01/04/2003 -0500, you wrote: > >Michael writes: >> 2) The amendment to 2.11 End-Of-Line Handling >> (http://www.w3.org/TR/xml11/#sec2.11) means that its possible for 0x85 >> and 0x2028 to occur in the XML declaration before the version of the >> document is determined to be 1.1. > >The XML declaration in XML 1.1 will continue to be restricted to ASCII > There is no way for you to detect a #x85 codepoint ><?xml' and version in any case since until you read the >encoding declaration you are not certain to know what the encoding of > Therefore, the value of any non-ASCII codepoint >cannot be reliably determined and will be prohibited from appearing in >the XML declaration. > >-Glenn > ----------------------------- Michael Glavassevich [EMAIL PROTECTED] 4B Computer Engineering University of Waterloo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
