TemplateStudio
TemplateStudio copied to clipboard
Onboard to new localization service
Need to integrate TDBuild into our CI pipelines.
We should update to the 2.0 vsixlangpack schema as documented at https://docs.microsoft.com/en-us/visualstudio/extensibility/localizing-vsix-packages?view=vs-2022 and https://docs.microsoft.com/en-us/visualstudio/extensibility/vsix-language-pack-schema-2-0-reference?view=vs-2022.
Our current vsixlangpacks use an old schema. See https://github.com/microsoft/TemplateStudio/blob/dev/code/src/Installer/de-DE/Extension.vsixlangpack.
.vsixmanifest and .vsixlangpack files may not be good candidates to integrate into the pipeline since they aren't expected to change frequently, the EULAs are already localized by VS and checked in, and their layout on disk may need to change to integrate with the pipeline, which adds unnecessary complexity.
Added comments to templatestrings.json files with https://github.com/microsoft/TemplateStudio/commit/efae41eb92e52e5c30628c9fbc09f94b373c49b6.
The comments follow the resjson format and help translators provide better translations.
Added vstemplate files to the localization pipeline with 1596846538fdf200c2901cef1bf95c40063b4361 and parent commits to refactor the WinUI vstemplate files.
The ordering in JSON files needs to match for the resources to be translated correctly. See https://github.com/microsoft/TemplateStudio/commit/d7e6b8b5ca4c1174e0708401236905e1023c84bf.
Closing as completed.
Run the localization pipeline, download and extract the TDBuild artifact from the pipeline, then run Import-TDBuild to import the localized files.