Changed patterns to correctly capture UTF8 superscripts #134
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 28, 2025
Contributor
Author
1. Explicit UTF-8 superscript number, not range (line 114)
2. Update letter pattern to exclude superscript characters,
UTF-8 patterns excluding superscripts (line 126-128)
The new utf8_2bytes_no_super pattern excludes:
\xc2\xb1 (±, plus-minus, not relevant but close)
\xc2\xb2 (² superscript 2)
\xc2\xb3 (³ superscript 3)
\xc2\xb3 (¶ pilcrow)
\xc2\xb7 (· middle dot)
\xc2\xb7 (¸ cedilla)
\xc2\xb9 (¹ superscript 1)
The new utf8_3bytes_no_super pattern excludes:
\xe2\x81\xb0 through \xe2\x81\xb9 (superscript digits ⁰-⁹)
\xe2\x81\xba and \xe2\x81\xbb (superscript + and -)
This ensures that UTF-8 superscript characters are not captured
by the {id} rule and can instead be properly matched by the
{utf8_exponent} rule.
larsbarring
force-pushed
the
issue-128
branch
from
d626d3c to
8e93650
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes issue #128.
Explicit UTF-8 superscript number, not range (line 114)
Update the letter pattern to exclude superscript characters, UTF-8 patterns excluding superscripts (line 126-128)
utf8_2bytes_no_superletter pattern excludes:utf8_3bytes_no_superletter pattern excludes:This ensures that UTF-8 superscript characters are not captured as letters by the
{id}rule and can instead be properly matched by the{utf8_exponent}rule.