← 返回首页
Support confusables · Issue #7946 · unicode-org/icu4x · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Resetting focus

Support confusables #7946

New issue
New issue

Description

ICU4C uspoof.h implements Unicode spoof detection algorithms (from UTS 39).

ICU4X has a narrower scope than ICU4C and explicitly plans not to implement spoof detection in the core library, but exposing a good confusables API is a part of it, and is easier to do now that we can directly consume the UCD.

I'm not sure which crate this would go in. Probably icu_properties?

Beyond confusables, spoof checking needs idstat and idtype, but those are just enum props and easy to expose.

The API here would mostly just be exposing skeleton(A) and skeleton(A) == skeleton(B). Not sure what an efficient data model would be. We might be able to stuff most of this a CPT, with an exceptions table for multi-byte things. I wonder what ICU4C does.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-unicodeComponent: Props, sets, triesU-chromiumFeatures from ICU4C that Chromium uses that do not fit under existing U-chromium-foo labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    • Open in GitHub Copilot app

    Footer

    © 2026 GitHub, Inc.