-
Notifications
You must be signed in to change notification settings - Fork 9k
Clean up a bunch of unused localizations #19613
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
base: main
Are you sure you want to change the base?
Conversation
carlos-zamora
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow. It's cool to see all the changes we've made to Terminal over the years. Thanks for cleaning up the resources!
I really just have that one open question about the MinMaxCloseControl resources.
| <data name="WindowCloseButton.[using:Windows.UI.Xaml.Automation]AutomationProperties.Name" xml:space="preserve"> | ||
| <value>Close</value> | ||
| </data> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's weird that this one is removed, but the one underneath it is kept.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at MinMaxCloseControl.xaml, looks like we have CloseButton, MaximizeButton, and MinimizeButton. No WindowCloseButton etc (except there is WindowMinimizeButtonToolTip).
I think the right move here is to rename the resources so that they're attached to CloseButton etc. instead of WindowCloseButton etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They're just not used, actually. Mike noted in #11680 that he had to manually create and display the tooltips.
The accessibility stuff has been unhooked since then too. In 2021.
| </data> | ||
| <data name="TerminalPage_PaneMovedAnnouncement_ExistingWindow" xml:space="preserve"> | ||
| <value>Active pane moved to "{0}" tab in "{1}" window</value> | ||
| <comment>{Locked="{0}"}{Locked="{1}"}This text is read out by screen readers upon a successful pane movement. {0} is the name of the tab the pane was moved to. {1} is the name of the window the pane was moved to. Replaced in 1.19 by TerminalPage_PaneMovedAnnouncement_ExistingWindow2</comment> | ||
| </data> | ||
| <data name="TerminalPage_PaneMovedAnnouncement_ExistingWindow2" xml:space="preserve"> | ||
| <value>Active pane moved to "{0}" window</value> | ||
| <comment>{Locked="{0}"}This text is read out by screen readers upon a successful pane movement. {0} is the name of the window the pane was moved to.</comment> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we keep TerminalPage_PaneMovedAnnouncement_ExistingWindow and update it with the correct value instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eh. It's not worth causing the loc to "churn" while everything rediscovers that the old key has the new value.
Well, they might be unused. A weird hacked-together PowerShell script I wrote told me.