UAX #14 rev. 57, Section 5.1 GL: should the description name the HY and HH exceptions of LB12a?

The GL description names SP and ZW as what can override the no-break prohibition. LB12a also allows a break before GL after HY and HH, which the HH description explains as widespread practice.

Consequence

U+0061, U+002D HYPHEN-MINUS, U+00A0 NO-BREAK SPACE, U+0062: a break after the hyphen, which the GL description does not mention.

Proposed correction

Mention the HY and HH exceptions of LB12a in the GL description.

Issued by

Unicode Consortium — Unicode Technical Committee

Act

UAX #14 revision 57 (Unicode 18.0.0)

Place

Section 5.1, class GL

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.

Non-breaking characters prohibit breaks on either side, but that prohibition can be overridden by SP or ZW. In particular, when NO-BREAK SPACE follows SPACE, there is a break opportunity after the SPACE

Allowing a break after HH or HY matches widespread implementation practice and supports a common way of handling special line breaking of explicit hyphens

How to check it without Arxo's tools

1. Open UAX #14 revision 57 (Unicode 18.0.0), Unicode Consortium and find Section 5.1, class GL; class HH. 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).
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-0466, https://arxo.io/findings/ARXO-2026-0466/ (status as of 2026-10-31). Data: ARXO-2026-0466.json.