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

Fix spelling mistake in german #3250

Merged
merged 6 commits into from
May 17, 2023
Merged

Fix spelling mistake in german #3250

merged 6 commits into from
May 17, 2023

Conversation

speedfighter
Copy link
Contributor

@speedfighter speedfighter commented May 14, 2023

WindowsTerminal_cd667uQz77

The spelling mistake on the screenshot will be fixed with this pull request.
There was a missing space.

Microsoft Reviewers: Open in CodeFlow

@speedfighter speedfighter requested a review from a team as a code owner May 14, 2023 18:45
@yao-msft
Copy link
Contributor

Looks like this issue exists in all other localized languages strings. Filed localization bug internally.

@@ -702,7 +702,7 @@ Sie können über die Einstellungsdatei „winget settings“ konfiguriert werde
<value>Zeigt verfügbare Upgrades an und führt sie aus.</value>
</data>
<data name="Usage" xml:space="preserve">
<value>Verwendung: {0}{1}</value>
<value>Verwendung: {0} {1}</value>
<comment>{Locked="{0}","{1}"} Message displayed to provide the user with instructions on how to use a command. {0} is a placeholder replaced by the program name (e.g. 'winget'). {1} is a placeholder replaced by the pattern for using the selected command.</comment>
Copy link
Contributor

Choose a reason for hiding this comment

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

Actually. this issue could be fixed by updating locked words in comments in this file here

to be {Locked="{0} {1}"}

@speedfighter, would you make that change since you found this issue? Or I can make that change if you are not comfortable making it.

Copy link
Contributor

Choose a reason for hiding this comment

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

Same for this line here and here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can make these changes when I'm at home.

@speedfighter
Copy link
Contributor Author

I have implemented the changes. I hope I understood you correctly.

@speedfighter
Copy link
Contributor Author

I have implemented the changes. I hope I understood you correctly.

Or do I need to revert the changes made in my first commit?

@yao-msft
Copy link
Contributor

I have implemented the changes. I hope I understood you correctly.

Or do I need to revert the changes made in my first commit?

Hi @speedfighter, I'm sorry I should make my comments more clear. All localization changes need to go to en-US file at src/AppInstallerCLIPackage/Shared/Strings/en-us/winget.resw

Files under Localization folder will be overwritten when we do a localization update, so no changes under Localization folder will take effect.

Also please only lock the 3 places I mentioned at line 714, 845 and 1019 in en-US file.

Thanks

@@ -872,7 +872,7 @@ Sie können über die Einstellungsdatei „winget settings“ konfiguriert werde
</data>
<data name="InvalidArgumentValueError" xml:space="preserve">
<value>Der für das Argument "{0}" angegebene Wert ist ungültig. gültige Werte sind: {1}</value>
<comment>{Locked="{0}","{1}"} Error message displayed when the user provides an invalid command line argument value. {0} is a placeholder replaced by the argument name. {1} is a placeholder replaced by a list of valid options.</comment>
<comment>{Locked="{0} {1}"} Error message displayed when the user provides an invalid command line argument value. {0} is a placeholder replaced by the argument name. {1} is a placeholder replaced by a list of valid options.</comment>
Copy link
Contributor

Choose a reason for hiding this comment

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

This change is not needed as {0} and {1} are separate

@speedfighter
Copy link
Contributor Author

Sorry. I don't saw that your lines was in the en-US file.
Now I think I've made all changes which are necessary to fix this bug.

@yao-msft
Copy link
Contributor

Sorry. I don't saw that your lines was in the en-US file. Now I think I've made all changes which are necessary to fix this bug.

Thanks for the contribution!

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