ARXO-2026-0467 · Reported
UAX #14 rev. 57, Section 5.1 EX: should the exception list for EX include PR?
The EX description says these characters behave like closing characters except in relation to PO and NS. LB25 keeps CL and CP before PR in numeric context but not EX, so EX also differs in relation to PR.
Consequence
U+0031 U+0021 U+002B U+0032 breaks after the exclamation mark; U+0031 U+0029 U+002B U+0032 does not.
Proposed correction
Add PR to the exception list of EX, or state that LB25 treats EX differently from CL.
- Issued by
- Unicode Consortium — Unicode Technical Committee
- Act
- UAX #14 revision 57 (Unicode 18.0.0)
- Place
- Section 5.1, class EX, against LB25
- 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.
Characters in this line break class behave like closing characters, except in relation to postfix ( PO ) and non-starter characters ( NS ).NU ( SY | IS )* CL × PR
How to check it without Arxo's tools
- Open UAX #14 revision 57 (Unicode 18.0.0), Unicode Consortium and find Section 5.1, class EX, against LB25; rule LB25. Compare the text with the quotation above. A copy is kept in this register: 296df5332aefe695-tr14-57.html (SHA-256
296df5332aefe695b4951b511288b118bc6a7b43db7fadfd60f6062096acc7c0, copy of the official file). - 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
| Date | Institution | Channel | Reference |
|---|---|---|---|
| 2026-10-31 | Unicode Consortium — one PDF with 18 reports | Message-ID: <CAH-SH71i9Rky90g_YO=CGO3xx7NZFnEg==fkn2PuRp_7WpgjHw@mail.gmail.com> |
Responses
No response recorded.
History
- 2026-10-31Confirmed by Arxo
- 2026-10-31Entered in the register
- 2026-10-31Reported to Unicode Consortium (e-mail)
Cite this record
Arxo Law, Arxo Findings Register, ARXO-2026-0467, https://arxo.io/findings/ARXO-2026-0467/ (status as of 2026-10-31). Data: ARXO-2026-0467.json.