-
Notifications
You must be signed in to change notification settings - Fork 253
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
Installing three-letter ISO localized packages are not compatible. #10805
Comments
I think there's a dup in #2245. @kartheekp-ms can you please verify. |
Triage: @jebriede can you please take a look. |
@v-luzh - does this work on NuGet 5.8 or earlier? |
@aortiz-msft it repro on VS D16.8\30420.98 with implicit NuGet 5.8.0.6776 as below screenshot, but the difference is it didn't show error NU1701. |
Closing as dup of #2245 |
Why was this closed as a dup? Seems like a different issue with three letter locales? This is preventing certain locales from working: |
This is still a problem today. I hope there is a fix to support three-letter locales. |
@JonDouglas can this be re-opened? This still a problem after three years. @nkolev92 had pointed out the issue in another issue (I missed the link) is here |
Details about Problem
When installing any package that has been localized with resource assemblies & contains a three-letter ISO name, it will fail to install.
https://docs.microsoft.com/en-us/nuget/create-packages/creating-localized-packages
NuGet product used (NuGet.exe | Visual Studio | MSBuild.exe | dotnet.exe):
16.9, dotnet SDK 5.0.202
Worked before? If so, with which NuGet version:
N/A, but does work with 2 letter locale packages such as
zh-CN
(i.e. https://www.nuget.org/packages/Humanizer.Core.zh-CN/2.9.7)Repro steps and/or sample project
dotnet new
.NET 5 console applicationInvestigation
https://docs.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo?view=net-5.0#culture-names-and-identifiers has some interesting cases around availability of two-letter vs. three-letter.
https://stackoverflow.com/a/21042311/1048571 seems to suggest that CultureInfo limitations too. The list https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes doesn’t include fil in it. However 639-2 & 639-3 do include it.
InvariantCulture should handle this however? I’m not aware of any specific code in NuGet that limits as this fails in both VS & dotnet CLI which have different compat code for installing.
The text was updated successfully, but these errors were encountered: