UAX #29 rev. 49, Section 4.3: how is the union and intersection in the Basic Name Validation set grouped?

The set “[ \p{name=/COMMA/}\p{name=/FULL STOP/}&\p{p} …” mixes union and intersection without brackets. UTS #18 does not fix one precedence and recommends brackets.

Consequence

U+236A APL FUNCTIONAL SYMBOL COMMA BAR (So) is in the set under one grouping and out of it under the other.

Proposed correction

Add brackets, for example [[\p{name=/COMMA/}\p{name=/FULL STOP/}]&\p{p}].

Issued by

Unicode Consortium — Unicode Technical Committee

Act

UAX #29 revision 49 (Unicode 18.0.0)

Place

Section 4.3, Basic Name Validation set

Record

Question of reading or data

Class

Question of reading or data

Where it arose

The text of the act

Arxo's conclusion

Confirmed

Official text

Unchanged at last check

Last checked

2026-10-31

Evidence

Contradiction within the text. Quotations are verbatim from the official material; translations are ours and marked.

[ \p{name=/COMMA/}\p{name=/FULL STOP/}&\p{p} \p{whitespace}-\p{c} \p{alpha}

It is a lenient, non-language-specific set, and could be tailored where only a limited set of languages are permitted

How to check it without Arxo's tools

1. Open UAX #29 revision 49 (Unicode 18.0.0), Unicode Consortium and find Section 4.3, Basic Name Validation set. Compare the text with the quotation above. A copy is kept in this register: 60fb49ee640a154d-tr29-49.html (SHA-256 60fb49ee640a154d9e40468306c6b283edcef73be3af5ede778107b4787bdec8, copy of the official file).
2. The finding holds if the quoted passages read as shown and the comparison gives the result stated at the top of this page. If it does not, write to us with the record ID.

How this finding was made

AI agents read the annexes and the data files and compared them; the examples were run through published implementations. An AI coordinator checked each place against the full annex and the trackers, and two further AI models checked the report before filing.

Responsible institutions

• Unicode Consortium — publishes the annex and the Unicode Character Database

Reported to

Responses

No response recorded.

History

1. 2026-10-31Confirmed by Arxo
2. 2026-10-31Entered in the register
3. 2026-10-31Reported to Unicode Consortium (e-mail)

Cite this record

Arxo Law, Arxo Findings Register, ARXO-2026-0471, https://arxo.io/findings/ARXO-2026-0471/ (status as of 2026-10-31). Data: ARXO-2026-0471.json.