Skip to content
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

Localized file check-in by OneLocBuild Task: Build definition ID 615: Build ID 216216 #476

Closed

Conversation

azure-pipelines[bot]
Copy link
Contributor

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/icxLocBug 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.

@@ -3361,7 +3368,7 @@
{
"id": "Syntax error at line {LineNumber} near command '{Command}'.",
"message": "Syntax error at line {LineNumber} near command '{Command}'.",
"translation": "Error de sintaxis en la línea {LineNumber} cerca del comando '{Command}'.",
"translation": "Syntax error at line {LineNumber} near command '{Command}'.",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Syntax error at line {Lin

why is the translation reverting to english?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have had this issue in the past when existing strings had some modifications. However, in this case there have been no modifications to this particular strings AFAIK. I'll check with loc team if this is expected.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other PR has the correct translations hence we can close this one without merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants