No, it's not a bad idea, and these 4 lines of bash script contain no solid reasoning, argument, or business logic as to why helping the other 80% of the world's population is a very bad idea. Doing internationalization without support libraries is a very bad idea, as this sample code helps illustrate.
It is PowerShell.
Why internationalization of commands is a very bad idea
41–50 of 52 posts
Re: Why internationalization of commands is a very bad idea
#42Re: Why internationalization of commands is a very bad idea
#43In my language, there isn't No, there is only "YES" and "MAYBE".
Mind pointing out which one? http://www.omniglot.com/language/phrases/yesnomaybe.htm
Re: Why internationalization of commands is a very bad idea
#44Earlier quoted context omitted.
Mind pointing out which one? http://www.omniglot.com/language/phrases/yesnomaybe.htm
Could be Japanese, depending on the situation. http://www.japanese-language.aiyori.org/article6.html
Re: Why internationalization of commands is a very bad idea
#45That is horrible code, there is not just de-de but also de-at and de-ch and fr-fuck-it-I-will-not-look-it-up etc. And the program should treat all equally. ( I would suggest equally badly.)
Re: Why internationalization of commands is a very bad idea
#46This problem also applies to MediaWiki. They decided to internationalize pretty much everything, too. Not only functions are translated; the functionality of some URL parts also depends on the language - and you'll get a lot of duplicates when more languages are enabled.
Re: Why internationalization of commands is a very bad idea
#47Earlier quoted context omitted.
It's a terrible idea unless you can force the command to accept arguments in a specific language. Do you expect someone to iterate all the possible variants of "yes"?
With the proper support libraries, Da/Yes/Ha/Ja/etc/etc/etc it's trivial.
There is literally no way to know what languages are supported, this is impossible to enumerate, and what might pass for correct at one time might be adjusted later to better reflect conversational usage.
It's like insisting you could possibly know all the honorifics a personal name might have. If you think you can you're deluding yourself.
Re: Why internationalization of commands is a very bad idea
#48Earlier quoted context omitted.
Mind pointing out which one? http://www.omniglot.com/language/phrases/yesnomaybe.htm
Perhaps Japanese. The meaning of "Hai" is more like "true" than "yes".
Re: Why internationalization of commands is a very bad idea
#49Earlier quoted context omitted.
In PowerShell you do the following: New-PSSessionOption -Culture=de-DE Might be worthwhile looking up the PowerShell reference before making comments like that...
Sure, but how long is this solution available and in how many years do you think it will be deprecated? Getting a bit offtopic though.