From: Junio C Hamano <gitster@pobox•com>
To: Michael J Gruber <git@drmicha•warpmail.net>
Cc: git@vger•kernel.org
Subject: Re: [RFC/PATCH 2/5] glossary: introduce glossary lookup command
Date: Thu, 11 Dec 2014 12:06:45 -0800 [thread overview]
Message-ID: <xmqqiohidk8a.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <5489B70E.2040604@drmicha.warpmail.net> (Michael J. Gruber's message of "Thu, 11 Dec 2014 16:23:58 +0100")
Michael J Gruber <git@drmicha•warpmail.net> writes:
>> I wondered if we want to also have the associated documentation in
>> response to a query, but I am not sure how well that would go
>> without having a translated glossary at least. I.e. pulling the
>
> Yes, I think we would need something different then. The glossary
> entries are asciidoc which we can't format easily from the glossary
> command. I really think of the glossary command as being orthogonal to
> the definitory glossary. I guess I should name it "translate" instead.
> ...
>
>> original from glossary-content.txt would produce something like
>> this:
>>
>> $ LANG=de git glossary -l blob object
>> Blob-Objekten
>> Untyped <<def_object,object>>, e.g. the contents of a file.
>>
>> which is not ideal.
I didn't mean the AsciiDoc part, though. I meant that the contents
are not in LANG=de, which is not ideal. So translating "blob object"
to whatever it is called in LANG=de, without the description, is the
best we can do without having a translated documentation set.
next prev parent reply other threads:[~2014-12-11 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 15:38 [RFC/PATCH 0/5] git-glossary Michael J Gruber
2014-12-08 15:38 ` [RFC/PATCH 1/5] glossary.h: generate a glossary list from the Makefile Michael J Gruber
2014-12-08 15:38 ` [RFC/PATCH 2/5] glossary: introduce glossary lookup command Michael J Gruber
2014-12-10 22:50 ` Junio C Hamano
2014-12-11 15:23 ` Michael J Gruber
2014-12-11 20:06 ` Junio C Hamano [this message]
2014-12-08 15:38 ` [RFC/PATCH 3/5] glossary: man page Michael J Gruber
2014-12-08 15:38 ` [RFC/PATCH 4/5] l10n: git-glossary Michael J Gruber
2014-12-08 16:04 ` [RFC/PATCH 0/5] git-glossary Michael J Gruber
2014-12-08 16:16 ` Christian Couder
2014-12-08 16:41 ` Michael J Gruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqiohidk8a.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox