Localized file check-in by OneLocBuild Task: Build definition ID 1159: Build ID 1988622

[dotnet-bot]

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.

[dougbu]

/fyi

• @jonfortescue this PR correctly excludes the files we want excluded (unlike Localized file check-in by OneLocBuild Task: Build definition ID 1159: Build ID 1969939 #43428). Thanks again for that Arcade fix.
• @cristianosuzuki77 I know it's by design that loc handbacks initially overwrite translations w/ English text as new files (or strings) are included in the loc project. But please let the translators know they can confirm and reuse the strings checked into our 'main' branch.

[dougbu]

/fyi @dotnet/aspnet-build it's relatively easy to see whether PRs like this are ready to be merged:

1. Head to the latest aspnetcore-localization or spa-templates-localization build
2. Click on the OneLocBuild job
3. Click on the OneLocBuild step
4. Scroll down almost to the bottom of the console log,
5. Check the lines immediately after Generating localization completeness status data...

For this PR, the JSON files are all 100% localized for 13 languages which means they're done. However, the three WXL files of interest are only 8% localized for 13 languages.

[wtgodbe]

However, the three WXL files of interest are only 8% localized for 13 languages.

How do we get an idea of when that'll be done?

[dougbu]

How do we get an idea of when that'll be done?

Whenever OneLocBuild adds a new commit to the branch, check I guess.

I seem to remember the loc team has a 5 workday SLA. Is that correct @cristianosuzuki77❔And, will things be any faster due to the existing translations in the target branch❔

[dougbu]

@cristianosuzuki77, @jonfortescue, or anyone else familiar w/ loc team SLAs: Why has this PR not been updated for 9 days❔ The OneLocBuild status has actually not changed in almost two weeks, since 211def7 was added to the previous PR (#43428) for the new WXL localization. We're running out of time…

[dougbu]

This PR was messed up by a preparatory change on the loc side to unblock localization of .wxl files.