On Mon, May 15, 2017 at 11:38:54PM +0200, Ingo Schwarze wrote: > 5. If possible, install to man/language/manN, without any "_", ".", > or "@": KISS. There are rare exceptions, most notably zh_CN > vs. zh_HK vs. zh_TW. > Never include the encoding in the path name, and make sure > the /language/ part never contains "." (a dot).
What are the other exceptions ? > If you think the above makes sense, i'm likely to do some of that > myself while continuing work on USE_GROFF, but i don't promise > to check all 500 pages, of course. Sounds like a good plan. > I don't say that translating documentation is always a good idea. > Quite to the contrary, i think that it is not unusual to do more > harm than good. But the reasons why that is so are purely practical > reasons (mostly excessive workload and translations being poor in > the first place and getting outdated over time); in principle, > having information available in more than one language could make > the world a better place, and tooling should not discourage people > trying to prove that for some projects, it is also feasible in > practice. There might also be cases where the reference documentation is not english because the project is not based in an english speaking country. I remember when I started playing with japanese ports. A big difficulty was bootstrap, because the code comments were in japanese, and most decent documentation was in japanese as well. Didn't help that we didn't have any decent editor handling japanese at the time -- hence our antiquated jvim, nor anything that could print japanese... the size of the fonts were a problem with printers at the time -- hence kanjips. The situation is better these days, but there do exist some worthwhile projects where the reference texts are NOT in english.
