Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

With NFKC variant considered harmful #1974

Open
aphillips opened this issue Jan 16, 2025 · 1 comment
Open

With NFKC variant considered harmful #1974

aphillips opened this issue Jan 16, 2025 · 1 comment
Labels
ietf https://ietf.org/ needs-resolution i18n expects this item to be resolved to their satisfaction. s:modern-network-unicode https://datatracker.ietf.org/doc/draft-bormann-dispatch-modern-network-unicode/

Comments

@aphillips
Copy link
Contributor

aphillips commented Jan 16, 2025 •
edited
Loading

Proposed comment

https://datatracker.ietf.org/doc/draft-bormann-dispatch-modern-network-unicode/

Section 5.7 defines a "With NFKC" variant.

This is probably a Bad Idea.

NFKC is destructive and also might be incomplete in accomplishing something useful. Mentioning the K forms is probably fine, but by not defining this, we stay away from the problems it produces. Note that we have this note in charmod-norm:

Unicode compatibility decomposition removes meaning from the text that it is applied to. That means that this normalization step produces the most promiscuous matches. Some developers and specification authors find this level of normalization attractive because it appears to bring together many strings that are logically similar, but this level of normalization has limited utility in actual practice and has side effects that confuse users. This normalization step is presented for completeness, but it is not generally appropriate for use on the Web.
@aphillips aphillips added ietf https://ietf.org/ needs-resolution i18n expects this item to be resolved to their satisfaction. pending Issue not yet sent to WG, or raised by tracker tool & needing labels. s:modern-network-unicode https://datatracker.ietf.org/doc/draft-bormann-dispatch-modern-network-unicode/ labels Jan 16, 2025
@aphillips aphillips removed the pending Issue not yet sent to WG, or raised by tracker tool & needing labels. label Feb 11, 2025
@aphillips
Copy link
Contributor Author

sent via email
https://lists.w3.org/Archives/Public/public-i18n-core/2025JanMar/0037.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ietf https://ietf.org/ needs-resolution i18n expects this item to be resolved to their satisfaction. s:modern-network-unicode https://datatracker.ietf.org/doc/draft-bormann-dispatch-modern-network-unicode/
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aphillips