[coldtea]

>- i18n is made hard

It's also mostly redundant. I'd expect CLI users to be able to parse flags and --help messages in english.

And I'm not saying it as a native english speaker -- which I'm not. Without english knowledge you can't parse 99% of existing, never to be i18n standard UNIX commands, flags, and manpages.

[thayne]

> Without english knowledge you can't parse 99% of existing, never to be i18n standard UNIX commands, flags, and manpages.

That makes me sad.

[coldtea]

That makes me happy. I'm all for national languages, ethnic nuances etc (I'm not English-native-speaker myself), great spell checkers, voice recognition, fonts, etc for all languages.

But for text work (writing, reading, etc).

Not on my fucking programming languages (like bizarro foreign variable names in source code), and ideally, not on my CLI either.

Let's have a common universal language in our domain.

Doctors get to use latin names and common terms for tons of medical staff whatever their country. Pilots get to speak english with every control tower all around the world.

Computer work should have some of that too.

[thayne]

There's a difference between having source code and CLI commands in a hodge-podge of languages and not having translations of man pages.

[e12e]

I'm not sure if 99% is accurate - unless you intentionally include internal tooling ("standard UNIX commands" implies not).

Now, if you mean "actual UNIX", I'm not sure - but at least gnu is pretty widely translated. Not sure where the bsds stand on this.

[realusername]

> which I'm not. Without english knowledge you can't parse 99% of existing, never to be i18n standard UNIX commands, flags, and manpages.

Most of the standard GNU commands are translated, at least I can't think of any which is not.