Re: [RFC/PATCH 0/5] git-glossary

From: Michael J Gruber <git@drmicha.warpmail.net>
Date: Dec 8, 2014, 16:41 UTC
Message-ID: <5485D4BF.7010700@drmicha.warpmail.net>
In-Reply-To: <CAP8UFD0yRKRPj3x6jZoL72jkzs0T2vZ0HZVi46zX0gzXqGv_Sw@mail.gmail.com>

Christian Couder schrieb am 08.12.2014 um 17:16:

Show 12 quoted lines

> On Mon, Dec 8, 2014 at 4:38 PM, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> More and more people use Git in localised setups, which usually means
>> mixed localisation setups - not only, but also because of our English
>> man pages.
>>
>> Here's an attempt at leveraging our current infrastructure for helping
>> those poor mixed localisation folks. The idea is to keep the most
>> important iterms in the glossary and translate at least these.
> 
> If the problem is related to all the man pages, shouldn't the solution
> apply to all the man pages?

Huh? I'm not going to translate the man pages.

This is about providing a localised glossary. It just so happens that we have a glossary as a man page already, so I'm leveraging it.

>> 1/5: generate glossary term list automatically from gitglossary.txt
>> 2/5: introduce git-glossary command which helps with lookups
> 
> Couldn't you improve git-help ?

I think git help is good as is.

Or do you suggest integrating the glossary lookup command in "git help"? For my taste, "git help" does a lot of magic already (in terms of revolving "foo" in "git help foo"). What it does not do is translating. Integrating "glossary" in "help" would require the use of mode changing options to get the same functionality as "git glossary" and "git glossary foo". So, git help is really for help about commands, and git younameit for localised help about terms.

Michael