Skip to content

Fix some error correction for USourceData 9..12.1 - #1491

Merged
markusicu merged 1 commit into
unicode-org:mainfrom
eggrobin:𰴦≈𧤽
Aug 5, 2026

Hidden character warning

The head ref may contain hidden characters: "\ud883\udd26\u2248\ud85e\udd3d"
Merged

Fix some error correction for USourceData 9..12.1#1491
markusicu merged 1 commit into
unicode-org:mainfrom
eggrobin:𰴦≈𧤽

Conversation

@eggrobin

@eggrobin eggrobin commented Aug 5, 2026

Copy link
Copy Markdown
Member

I had failed to segment U+2793DUTC-02138 in #1370.

  • Approver: Feel free to merge on my behalf
    • rebase & merge one or more commits
    • squash & merge multiple commits into one

@eggrobin
eggrobin requested a review from markusicu August 5, 2026 20:30
keyField = "";
}
// U+2793 is ➓. Surely that is nonsense.
// U+2793D is 𧤽, similar to UTC-02139 ⿰角間 (now encoded at 𰴦).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does the smooshed value say UTC-02138 but the comment says UTC-02139?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The line in question is

UTC-02139;UK-2015;U+2793DUTC-02138;148.12;1145.081;⿰角間;UTCDoc L2/15-260 827

So UTC-02139 (now U+30D26 𰴦, kIRG_UKSource=UK-02139) was marked as similar to the pre-existing character U+2793D. It was also flagged as similar to UTC-02138 (now UK-02138, encoded as U+30D25 𰴥).

@markusicu
markusicu merged commit be583d5 into unicode-org:main Aug 5, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants