From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Subject: Re: [RFC/PATCH 0/5] git-glossary
Date: Mon, 08 Dec 2014 17:04:46 +0100 [thread overview]
Message-ID: <5485CC1E.4010401@drmicha.warpmail.net> (raw)
In-Reply-To: <cover.1418052470.git.git@drmicha.warpmail.net>
Michael J Gruber schrieb am 08.12.2014 um 16:38:
> 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.
>
> 1/5: generate glossary term list automatically from gitglossary.txt
> 2/5: introduce git-glossary command which helps with lookups
> 3/5: introduce git-glossary.txt, the man page for the command
> 4/5: git.pot update
> 5/5: sample de.po update
>
> Without 4/5 and 5/5, a few terms from the glossary can be translated
> already by coincidence with localised messages from some git commands.
>
> Michael J Gruber (5):
> glossary.h: generate a glossary list from the Makefile
> glossary: introduce glossary lookup command
> glossary: man page
> l10n: git-glossary
> l10n: de: git-glossary
>
> .gitignore | 2 +
> Documentation/git-glossary.txt | 48 ++
> Makefile | 8 +-
> builtin.h | 1 +
> builtin/glossary.c | 104 +++
> command-list.txt | 1 +
> generate-glossary.sh | 8 +
> git.c | 1 +
> po/de.po | 1382 ++++++++++++++++++++++++----------------
> po/git.pot | 1362 +++++++++++++++++++++++----------------
> 10 files changed, 1839 insertions(+), 1078 deletions(-)
> create mode 100644 Documentation/git-glossary.txt
> create mode 100644 builtin/glossary.c
> create mode 100755 generate-glossary.sh
While I did send 5/5 with UTF-8 encoding (or rather: git-sendemail
helpfully did so) it seems it doesn't get through. Anyways, this stuff
is here also:
https://github.com/mjg/git/tree/glossary-cmd
Or rather:
The following changes since commit a0de725a8ff02c1f2a9452c2234bee819242395c:
Sync with Git 2.2 (2014-11-26 13:20:21 -0800)
are available in the git repository at:
git://github.com/mjg/git glossary-cmd
for you to fetch changes up to 1265605787662a72c2457be0623a76d4d2a74bc1:
l10n: de: git-glossary (2014-12-08 16:26:31 +0100)
----------------------------------------------------------------
Michael J Gruber (5):
glossary.h: generate a glossary list from the Makefile
glossary: introduce glossary lookup command
glossary: man page
l10n: git-glossary
l10n: de: git-glossary
next prev parent reply other threads:[~2014-12-08 16:04 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
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 ` Michael J Gruber [this message]
2014-12-08 16:16 ` [RFC/PATCH 0/5] git-glossary 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=5485CC1E.4010401@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.