All, Some time ago (TPAC 2024??), I was tasked with reporting a gap in XML 1.0 5e and Namespaces in XML 1.0 3e. The issue is documented here: https://github.com/w3c/i18n-activity/issues/1903 The problem is that Unicode assigned a new bidirectional formatting character, U+061C ARABIC LETTER MARK, in 2013. This potentially affects the grammar of NameStartChar or at least merits an errata mention. The problem at that time was that the machinery for reporting errata on XML had broken down. In a hallway conversation, Philippe took the action to restore the mailing list and/or some mechanism for collecting reports. This is apparently solved, although a means of doing something about such reports may still not exist. In any case, this email serves as an attempt to record the issue. thanks, Addison -- Internationalization is not a feature. It is an architecture.
All, Some time ago (TPAC 2024??), I was tasked with reporting a gap in XML 1.0 5e and Namespaces in XML 1.0 3e. The issue is documented here: https://github.com/w3c/i18n-activity/issues/1903 The problem is that Unicode assigned a new bidirectional formatting character, U+061C ARABIC LETTER MARK, in 2013. This potentially affects the grammar of NameStartChar or at least merits an errata mention. The problem at that time was that the machinery for reporting errata on XML had broken down. In a hallway conversation, Philippe took the action to restore the mailing list and/or some mechanism for collecting reports. This is apparently solved, although a means of doing something about such reports may still not exist. In any case, this email serves as an attempt to record the issue. thanks, Addison -- Internationalization is not a feature. It is an architecture.
All, Some time ago (TPAC 2024??), I was tasked with reporting a gap in XML 1.0 5e and Namespaces in XML 1.0 3e. The issue is documented here: https://github.com/w3c/i18n-activity/issues/1903 The problem is that Unicode assigned a new bidirectional formatting character, U+061C ARABIC LETTER MARK, in 2013. This potentially affects the grammar of NameStartChar or at least merits an errata mention. The problem at that time was that the machinery for reporting errata on XML had broken down. In a hallway conversation, Philippe took the action to restore the mailing list and/or some mechanism for collecting reports. This is apparently solved, although a means of doing something about such reports may still not exist. In any case, this email serves as an attempt to record the issue. thanks, Addison -- Internationalization is not a feature. It is an architecture.
All, Some time ago (TPAC 2024??), I was tasked with reporting a gap in XML 1.0 5e and Namespaces in XML 1.0 3e. The issue is documented here: https://github.com/w3c/i18n-activity/issues/1903 The problem is that Unicode assigned a new bidirectional formatting character, U+061C ARABIC LETTER MARK, in 2013. This potentially affects the grammar of NameStartChar or at least merits an errata mention. The problem at that time was that the machinery for reporting errata on XML had broken down. In a hallway conversation, Philippe took the action to restore the mailing list and/or some mechanism for collecting reports. This is apparently solved, although a means of doing something about such reports may still not exist. In any case, this email serves as an attempt to record the issue. thanks, Addison -- Internationalization is not a feature. It is an architecture.
All, Some time ago (TPAC 2024??), I was tasked with reporting a gap in XML 1.0 5e and Namespaces in XML 1.0 3e. The issue is documented here: https://github.com/w3c/i18n-activity/issues/1903 The problem is that Unicode assigned a new bidirectional formatting character, U+061C ARABIC LETTER MARK, in 2013. This potentially affects the grammar of NameStartChar or at least merits an errata mention. The problem at that time was that the machinery for reporting errata on XML had broken down. In a hallway conversation, Philippe took the action to restore the mailing list and/or some mechanism for collecting reports. This is apparently solved, although a means of doing something about such reports may still not exist. In any case, this email serves as an attempt to record the issue. thanks, Addison -- Internationalization is not a feature. It is an architecture.