Back

@tonybaloney I think this is a bad idea, in general. When I need to work on an app or a system created/maintained by others, I don't want language to be a barrier.

@tiberiuichim this is the opposite of making it a barrier, this is providing optional, translated messages if the user requests them. All of Pythons builtin exceptions are in English, I’m seeing if you can print them in other languages

@tonybaloney When I login to a client's server that he needs my help with, I don't want to be confronted with an OS UI in their language. The same, I wouldn't be able to help them as easily if they present a traceback with errors in a language I don't know. And imagine the amount of help a newbie would get next time on a Discord channel, when they post a traceback with an error message that people wouldn't understand. Let's keep English as the lowest universal common thing, it's just easier.

@tonybaloney Needless to say, I'm not a fan at all of code variables and names that doesn't use English words.

@immibis @tonybaloney I'm not a native English speaker, so I can definitely understand the argument about colonization, specially if one's country has been a subject of Anglo colonial rule.

But as a software engineer, I see this is a path that leads to a lot of problems and complexity. Next thing you'll have a i18n team that needs to keep all translations up to date, before you can make a release, etc.

The intention is good, I recognize that, but I think the implied problems are not worth it.

@graingert good point, test suites would run under the default locale (English) but it would make sense to render the translation separately. The challenge is that the message is formatted eagerly. I’ve been replacing the format strings in C

@tonybaloney @graingert localizations as notes would solve a use case of someone using original error message to google up a solution, which would have a good coverage with the original error message