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.

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

Investigate potential NFC / NFD Unicode normalization issues for composed characters (accents etc.) #8225

Open
stephanegigandet opened this issue Mar 17, 2023 · 1 comment
Labels
🌐 i18n Regarding software localization 🎯 P1 candidate ⏰ Stale This issue hasn't seen activity in a while. You can try documenting more to unblock it.

Comments

@stephanegigandet
Copy link
Contributor

We currently do not normalize Unicode strings, so it is very likely that some string comparisons (e.g. to match strings to taxonomies) do not work if the strings and the taxonomy entries have different normalization.

This issue is to:

  • verify if we do have issues
  • add test cases for those issues
  • fix those issues

It may be a good thing to normalize all strings in OFF (taxonomies, database, API etc.) to a specific form.

@teolemon teolemon added 🌐 i18n Regarding software localization 🎯 P1 candidate labels May 11, 2023
@github-actions
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity.

@github-actions github-actions bot added the ⏰ Stale This issue hasn't seen activity in a while. You can try documenting more to unblock it. label Aug 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌐 i18n Regarding software localization 🎯 P1 candidate ⏰ Stale This issue hasn't seen activity in a while. You can try documenting more to unblock it.
Projects
Status: To discuss and validate
Development

No branches or pull requests

2 participants