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

Need APIs for unicode case mapping and case folding #4240

Closed
gafter opened this issue May 11, 2015 · 4 comments
Closed

Need APIs for unicode case mapping and case folding #4240

gafter opened this issue May 11, 2015 · 4 comments
Assignees
Milestone

Comments

@gafter
Copy link
Member

gafter commented May 11, 2015

The Unicode function for determining the category of Unicode characters (System.Globalization.CharUnicodeInfo.GetUnicodeCategory(char)) appears to reflect a fairly recent version of the Unicode standard. However, the functions for performing Unicode case mapping (culture-insensitive uppercase and lowercase) appear to reflect Unicode version 1.0. This mismatch was a severe impediment for implementing spec-compliant case folding in the VB compiler.

There is also no support whatsoever for performing case folding according to the Unicode specification (simplified or otherwise). APIs in the platform to do this would help with any language that, like VB, wants to depend on the Unicode specification for the meaning of case-insensitive identifiers.

@jkotas
Copy link
Member

jkotas commented May 12, 2015

cc @ellismg

@ellismg
Copy link
Contributor

ellismg commented May 12, 2015

This is something I'd like to do. I think the open issue is how we support this on Windows (since I think that we can get Case Folding functionality from ICU).

In general, we've tried to move away from the framework itself shipping globalization data and used the OS provided APIs instead. Since Windows doesn't currently expose a way to do case folding, we'd have to figure out what to do.

@karelz
Copy link
Member

karelz commented Mar 17, 2017

@tarekgh do we need a new API for this? If yes, we should move it to CoreFX. If not, let's remove "api addition" label.

@tarekgh
Copy link
Member

tarekgh commented Mar 17, 2017

Issue moved to dotnet/corefx dotnet/coreclr#17233 via ZenHub

@tarekgh tarekgh closed this as completed Mar 17, 2017
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 30, 2020
@msftgits msftgits added this to the Future milestone Jan 30, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants