[
https://issues.apache.org/jira/browse/XERCESJ-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855961#comment-17855961
]
Elliotte Rusty Harold edited comment on XERCESJ-1764 at 6/18/24 2:47 PM:
-------------------------------------------------------------------------
Can you be a little more specific with a precise reference to the spec that
establishes valid ranges? This is a very subtle point that has changed between
XML versions and editions. Production 85 of the original XML 1.0 spec
https://www.w3.org/TR/1998/REC-xml-19980210#NT-Letter says that 0x132 is not a
valid name token character.
I believe this is not a bug but a correct implementation of XML 1.0. The W3C
has not been a reliable steward of the XML spec.
was (Author: elharo):
Can you be a little more specific with a precise reference to the spec that
establishes valid ranges? This is a very subtle point that has changed between
XML versions and editions. Production 85 of the original XML 1.0 spec
https://www.w3.org/TR/1998/REC-xml-19980210#NT-Letter says that 0x132 is not a
valid character.
I believe this is not a bug but a correct implementation of XML 1.0. The W3C
has not been a reliable steward of the XML spec.
> NMToken is not validated correctly.
> -----------------------------------
>
> Key: XERCESJ-1764
> URL: https://issues.apache.org/jira/browse/XERCESJ-1764
> Project: Xerces2-J
> Issue Type: Bug
> Affects Versions: 2.12.2
> Reporter: Artur Smirnov
> Priority: Major
>
> Validate NMToken method doesnt work right
> (org.apache.xerces.util.XMLChar#isValidNmtoken). For example "AIJ" ("A" +
> 0x132) (0x132 in #xF8-#x2FF range). According w3org #xF8-#x2FF is a valid
> range. But for "AIJ" the method returns false.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
