You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This follows UAX's example procedure:
> An implementation of this loose matching rule can obtain the correct results when comparing two strings by doing the following three operations, in order:
> * remove all medial hyphens (except the medial hyphen in the name for U+1180)
> * remove all whitespace and underscore characters
> * apply toLowercase() to both strings
> * After applying these three operations, if the two strings compare binary equal, then they are considered to match.
and generating the name->codepoint PHF with the mapped ("normalised") names as keys.
This isn't a breaking change; in particular, any name that mapped to a character before will continue mapping to that same character.
0 commit comments