You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XML 1.0 5e and XML Names 1.0 use the construct NameStartChar shown above. The characters in names defined using NameStartChar were deliberately limited to avoid known problem characters at the time of adoption. Notable among the characters excluded from names are invisible formatting controls.
The character U+061C ARABIC LETTER MARK was added to Unicode in version 6.3 (in 2013). This character is similar to U+200F RIGHT-TO-LEFT MARK, which is not a NameStartChar. It is unusual that an invisible, non-spacing mark like this be added to Unicode. An XML name that consists of this single, invisible formatting control is thus valid, but it seems like a bug, not a feature.
(This issue was encountered in creating the MessageFormat 2.0 standard at Unicode, where we are attempting to use NCName and Name to define valid identifiers).
The downside, of course, is that very many implementations will not be aware if a change were made to NameStartChar.
This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:
§ url_for_the_issue_raised
The text was updated successfully, but these errors were encountered:
Proposed comment
https://www.w3.org/TR/REC-xml-names/#ns-qualnames
https://www.w3.org/TR/xml/#sec-common-syn
XML 1.0 5e and XML Names 1.0 use the construct
NameStartChar
shown above. The characters in names defined usingNameStartChar
were deliberately limited to avoid known problem characters at the time of adoption. Notable among the characters excluded from names are invisible formatting controls.The character U+061C
ARABIC LETTER MARK
was added to Unicode in version 6.3 (in 2013). This character is similar to U+200FRIGHT-TO-LEFT MARK
, which is not aNameStartChar
. It is unusual that an invisible, non-spacing mark like this be added to Unicode. An XML name that consists of this single, invisible formatting control is thus valid, but it seems like a bug, not a feature.(This issue was encountered in creating the MessageFormat 2.0 standard at Unicode, where we are attempting to use NCName and Name to define valid identifiers).
The downside, of course, is that very many implementations will not be aware if a change were made to
NameStartChar
.This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:
§ url_for_the_issue_raised
The text was updated successfully, but these errors were encountered: