Skip to content

<regex>: What names can and should regex_traits::lookup_collatename() recognize? #5393

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

Open
muellerj2 opened this issue Apr 6, 2025 · 0 comments
Labels
decision needed We need to choose something before working on this question Further information is requested regex meow is a substring of homeowner

Comments

@muellerj2
Copy link
Contributor

muellerj2 commented Apr 6, 2025

The title states this as one question, but it's really two.

First is an actual choice: Should the portable character names in the POSIX standard be recognized and translated bylookup_collatename()?

Cons:

  • These aren't actually names for locale-specific collating elements (which are defined in Chapter 7); they are symbolic names of characters for internal use in the POSIX standard.
  • TR1 was deliberately changed to not mandate that these are recognized by lookup_coolatename() (see the end of Section 2 of N1623).

Pro:

The second question is a technical issue that I don't have an answer to yet: Can we actually access the set of locale-specific (multi-character) collating elements or recognize them in a reasonable way using some Windows API? Or is there some other reasonable approach to recognize locale-specific collating elements like "ch" in Czech or "dzs" in Hungarian?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision needed We need to choose something before working on this question Further information is requested regex meow is a substring of homeowner
Projects
None yet
Development

No branches or pull requests

2 participants