Powertoys: Remove translation of PowerToy module names

[crutkas]

Currently items like "Color Picker" got translated. lets be consistent since items like FancyZones won't and will be an issue for getting debug information.

[fitojb]

My god, you really be killing a mosquito with a bazooka, aren’t you?

This is NOT the correct solution for the problem!

 The original issue was about a Spanish translation that is correct but doesn’t fit BY ONE LETTER on its allocated space.

[crutkas]

@fitojb this is actually a larger issue for constancy across all languages. Do you localize "Run" for powertoys run? How does that work for Korean vs Spanish vs Russian?

How does searching for a utility then work? How does the help docs work then if someone is expecting a localized version of that utility for the name?

What may seem like a small issue at face value is actually is a larger one for many reasons.

[fitojb]

I am a localizer, and I am well aware of the intricacies of providing a fully localized environment. I translate (and maintain consistency of) LibreOffice user interface and help, and before that I helped translate the Ubuntu operating system. I am well aware of the magnitude of the implications of localizing a user interface. I wouldn’t want to be condescending, but anyone can have a basic understanding of these by reading the Wikipedia article on internationalization and localization (i18n/l10n).

this is actually a larger issue for constancy across all languages. Do you localize "Run" for powertoys run? How does that work for Korean vs Spanish vs Russian?

Here is your mistake. Languages don’t have to be “consistent”, because we all use different linguistic resources (alphabets, idioms, expressions…). As somebody else in the issue already stated, descriptive names consisting only on regular English words like “Run” are not like trademarks, which can (and should) go untranslated everywhere.

[fitojb]

How does searching for a utility then work?

Those are internationalization (i.e., code) details. In the GNOME environment, application search works both with English and localized terms; translators provide versions of the English keywords for each app or settings command.

How does the help docs work then if someone is expecting a localized version of that utility for the name?

I am not to tell Microsoft how their teams should work because I don’t work there; you do. But if you want to know: Spanish-speaking countries (which I am familiar with due to my l10n experience) _expect_ a fully translated environment, without patchy UIs or complicated (to remember and to pronounce) English section names. (And I know for a fact that this expectation is not there in Italian, for example, but again: different languages, different cultures; not all languages have to be “consistent”.)

[fitojb]

We localizers always have an internal fight seeing the pervasive, creeping effect of computer-induced Anglicisms in our local languages. And in Spanish we take a lot of pride in our language and feel strongly about it. I though Microsoft had it clear—it even uses the word “culture” instead of “locale” to encompass all this!

[enricogior]

@fitojb
I understand your point of view and I tend to agree with you (I also speak Spanish and I know what you mean) but in this case we are in a gray area since some of the module names are "names" others are "description of the functionality provided by the module".
I assume you agree that PowerToys should not be localized, right?
And PowerToys is a collection of tools that could be stand alone tools with their own names.
When we started working on PowerToys, it was just a prototype and we didn't plan the modules names considering the localization issues (our mistake).
I would say that having a mix of localized and non localized module names is kind of awkward, and I also think that trying to localized FancyZones or PowerToys Run wouldn't make a lot of sense, so we would have to come up with new names for each language, not just translations.
So if we exclude those two options (1) mix of localized and not localized, and (2) all localized, the only one remaining is (3) all not localized.

[fitojb]

You’re of course allowed to choose new names that sound like marks and not descriptions, but until then, do not remove the translations.

[NekoGryphou]

Searching for help with a translated name is a real pain...
I'd much rather have the original name (which is much better in its basic language) than a translated name that looks like nothing and that will complicate the search for information.

[fitojb]

@NekoGryphou Please read carefully again. When internationalization is implemented properly, like in e.g. GNOME Shell or Unity, you can search with your preferred English terms and use a properly translated French interface. Similarly, a Linux emoji picker will allow you to use both English and CLDR-localized keywords to find characters. One option doesn’t exclude the other.

(And no, no language is better than another language. That line of thinking is colonial.)

[Jay-o-Way]

some of the module names are "names" others are "description of the functionality provided by the module"

PowerToys is/are still under construction, but I'm guessing it would be too much work to re-do the names of the individual toys??