[Localization] Switch from xlf to resx files #112
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The LibZipSharp repo has been fully onboarded into the OneLoc system,
and string translations are in progress.
XLF files and the XliffTasks NuGet will no longer be used. They have
been replaced by the OneLocBuild translation process which produces
translated RESX files.
Future changes to
LibZipSharp/Properties/Resources.resx
willtrigger a new OneLocBuild handoff for translation. Shortly after that,
the LCL files in the Localize folder will be automatically updated with
newly translated strings. This update will cause the OneLocBuild task
to open another PR which updates the RESX files used to produce
localized satellite assemblies.
This is the pull request automatically created by the OneLocBuild task
in the build process to check-in localized files generated based upon
translation source files (.lcl files) handed-back from the downstream
localization pipeline. If there are issues in translations, visit
https://aka.ms/ceLocBug and log bugs for fixes. The OneLocBuild wiki is
https://aka.ms/onelocbuild and the localization process in general is
documented at https://aka.ms/AllAboutLoc.