Intrusive localization

Since software vendors began to release localized versions of their products, users have an additional problem: how to return the interface to normal English?



Often, developers take the initiative and determine the localization language automatically without the possibility of changing it manually. And often it concerns not only the GUI but even the console utilities, for example, the Flex compiler for some time has strived to give error messages in Russian.

This creates huge problems for users:
- prof. terminology often does not have an unequivocal well-established translation, for example, SQL View can translate both “View” and “View”
- localized error messages cannot be “google” because Most forums, blogs and books use English quotes, and not Russian at all.
- the translation is almost always incomplete (see the screenshot where some of the inscriptions remained in Russian)
- prof. Users (for example, testers) can change the system locale depending on the tasks
')

Conclusion

The definition of a language and other locale settings in any software should be recommendatory. The user should always be available (for example from the menu) the ability to quickly return the interface to a usable form.