Open singhsarab opened 6 years ago
@anangaur
Any updates on this ?
@singhsarab , we have some ideas about improving the license URL experience, and we will look into the localization issue you pointed out as part of this. In the meantime, can you change the license page dynamically according to the user's culture?https://stackoverflow.com/questions/14393771/cultureinfo-in-javascript
@skofman1 @anangaur Any updates here ?
We are thinking about licensing improvements with packages. Not sure if those will include localization support. Something to think about @karann-msft?
@karann-msft Did you get a chance to look into this ?
I feel this is really important for us to have first class support for this. Localization for licenceUrl is vital for non-ENU customers.
@singhsarab the solution here is to create satellite packages for every loc. This will allow you to use a localized version of the license corresponding the to the loc of the nuget package.
Also did you take a look @skofman1 suggestion? Did that work for you?
There does not seem to be a way for making nuget metadata information localizable.
Example: licenseUrl is not localizable
Associated Customer Scenario: "License Info" points to ENU hardcoded content in the all cultures. Example, user with JPN OS will be taken to ENU license. Note: this impacts workflows both using nuget.org or via Visual Studio.
Expectation: licenseUrl is localizable so that users could actually see the EULA information in the respective language.