Tracking the addition of src/Resources.resx localization
- Dominant language
- C#
- Stars
- 2.9k
- Forks
- 576
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Right now, we use OneLoc for our localization, but the `src/Resources.resx` is still hooked up to our old method of XLIFF localization. To make sure the transition is smooth, I'll map out the steps needed to hook up these translations to OneLoc.
- [ ] Add the src/Resources.resx to the `LocProject.json.in` and have the CI create the initial `src/bgen/TranslatedAssemblies/Resources.*.resx` files
* https://github.com/xamarin/xamarin-macios/pull/19658
* https://github.com/xamarin/xamarin-macios/pull/19646
- [ ] Wait some days / a week for the OneLoc team to consume the new translations. Their tool will commit the not-yet-usable translated .lcl files into the `Localization` branch and the [xamarin.macios-legoChanges](https://devdiv.visualstudio.com/DevDiv/_build?definitionId=18272&_a=summary) pipeline will take those commits and make a PR (or a few PRs) into main.
- [ ] During the Sunday cron job CI (or ran manually with the 'manuallyCreateLocPR' flag selected) the [xamarin-macios-translations](https://devdiv.visualstudio.com/DevDiv/_build?definitionId=17751&_a=summary) pipeline will consume the .lcl files and create a PR into main with the usable translations into `src/TranslatedAssemblies/Resources.*.resx` where they will be available for our customers.
- [ ] By this point, we will want to remove any references to XLIFF or .xlf in our repo.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.