-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Insert seed localization for templates. #11040
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
Insert seed localization for templates. #11040
Conversation
The goal here is to eventually have all the localization be generated directly from your repos, but this starts to move us in that direction with the current translations statically checked in. @ryanbrandenburg, we will need to refresh this again after the other template changes which are still pending. After those changes are in, I'll do another PR. |
This is not blocked any more, as I've heard no concerns regarding this. |
@anurse, @mkArtakMSFT |
@phenning please rebase this to |
I don't have any concerns about this, but I also don't have a lot of context. Seems good to me :). |
Rebased and retargetted. |
...mplates/Web.ProjectTemplates/content/BlazorServerWeb-CSharp/.template.config/en/strings.json
Show resolved
Hide resolved
...es/Web.ProjectTemplates/content/RazorClassLibrary-CSharp/.template.config/fr-FR/strings.json
Show resolved
Hide resolved
Thanks @phenning. This is approved so I merged! |
Description
Localization seeding for the new localization mechanism for dotnet template engine templates in Visual Studio. Generated based on host file metadata in the templates and the localized strings we have in Visual Studio.
Customer impact
This is for the new localization mechanism for templates which is shipping in 16.3, allowing us to decouple localization from Visual Studio.
Regression?
No, this PR got missed merging for preview8.
Risk
Very low.