-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
CurrentCultureIgnoreCase string compare return false with Culture "en-US-POSIX" #27574
Comments
cc: @tarekgh (Tarek, is there a FAQ somewhere about POSIX/C culture handling that we can point people to? The question seems to come up a lot. If there's not already a discussion in the docs, maybe there could be?) |
@wli3 please look at the comment on the issue https://github.com/dotnet/corefx/issues/32250#issuecomment-420749205 @stephentoub I'll log issue to get this in the official documentation instead. |
logged the issue dotnet/docs#8179 |
In https://github.com/dotnet/cli/issues/10101, this seems to be happening by default on Unbuntu 18.04 on WSL. Should we be following up with WSL folks to make sure this isn't the default there? The docs issue says "We need to discourage users from using C or Posix cultures and always replace such usage with some other culture like en-US". In this case, I don't think the user has done anything deliberate, they're just using .NET Core on WSL. |
@nguerrera this is a good idea. if you have a contact from WSL we can contact them. |
cc @bitcrazed |
What is it about WSL that causes it to have this culture by default? An environment variable? |
Please close if this is by design of "en-US-POSIX". I want to make sure this is intentional. It is odd that a culture with prefix "en-US" will return false when comparing "nukeeper" and "NuKeeper"
The text was updated successfully, but these errors were encountered: