Skip to content

Legitimate Unicode normalization vs WorstFit ANSI #55

Description

@alistairwatts

Symbols within the "Derived Property: Full_Composition_Exclusion" section in https://www.unicode.org/Public/UNIDATA/DerivedNormalizationProps.txt are not the best choice for detecting WorstFit ANSI transformations.

Unicode normalization legitimately and deliberately transforms the Kelvin compatibility code point (within the range described above) to a capital K. Whilst this may not always be desired, it is not an indicator of WorstFit ANSI transformation.

I suggest transformation of code points with the "Derived Property: Full_Composition_Exclusion" are not highlighted as an issue, or are at least categorized differently.

(Plenty of Unicode "confusables" can be found at https://util.unicode.org/UnicodeJsps/confusables.jsp)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions