tinangel/ShaderTools — comment on commit cce10fbe52d6a433380d2bb0f2b8a3e294b28de6
File:  line 0
By ldo:

Sorry if I wasn’t clear, Karim. Yes, the user should be shown the names of the languages in terms they can understand, absolutely. But at the same time these should not be the names that the code uses internally to identify those languages. It’s best if internal codes don’t depend on any particular language. I like the GNU codes because 1) they’re already in common use for exactly this purpose, and 2) they allow for regional variations, as I said. As someone living in New Zealand, who speaks an English traditionally more influenced by Britain rather than the USA, I don’t like the idea that “English” must mean “US English”. We have our own GNU locale code, en_NZ, though en_GB is mostly acceptable as a substitute. :)

Similarly, a French-speaking person from Canada or Switzerland might object to the idea that “French” must mean “French as used in France”. So somebody might do localizations for ShaderTools for fr_CA and fr_CH, in addition to fr_FR. And similarly with Spanish. And so on.