From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH 0/2] i18n: Shell script translation infrastructure
Date: Sun, 3 Apr 2011 16:42:31 +0000 [thread overview]
Message-ID: <1301848953-31525-1-git-send-email-avarab@gmail.com> (raw)
Now that the C gettext infrastructure patches have made it to master
I'm submitting a series to do the same for our shell scripts. These
are the first two patches from:
git://github.com/avar/git.git ab/i18n-sh-only
The rest (to be submitted soon) are the patches marking up the
shellscripts themselves for translation.
Ævar Arnfjörð Bjarmason (2):
git-sh-i18n--envsubst: our own envsubst(1) for eval_gettext()
git-sh-i18n.sh: add no-op gettext() and eval_gettext() wrappers
.gitignore | 3 +
Documentation/git-sh-i18n--envsubst.txt | 36 +++
Documentation/git-sh-i18n.txt | 57 ++++
Makefile | 2 +
git-sh-i18n.sh | 17 ++
sh-i18n--envsubst.c | 444 +++++++++++++++++++++++++++++++
t/t0201-gettext-fallbacks.sh | 51 ++++
7 files changed, 610 insertions(+), 0 deletions(-)
create mode 100644 Documentation/git-sh-i18n--envsubst.txt
create mode 100644 Documentation/git-sh-i18n.txt
create mode 100644 git-sh-i18n.sh
create mode 100644 sh-i18n--envsubst.c
create mode 100755 t/t0201-gettext-fallbacks.sh
--
1.7.4.1
next reply other threads:[~2011-04-03 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 16:42 Ævar Arnfjörð Bjarmason [this message]
2011-04-03 16:42 ` [PATCH 1/2] git-sh-i18n--envsubst: our own envsubst(1) for eval_gettext() Ævar Arnfjörð Bjarmason
2011-04-03 19:05 ` Junio C Hamano
2011-04-10 22:43 ` Ævar Arnfjörð Bjarmason
2011-04-03 16:42 ` [PATCH 2/2] git-sh-i18n.sh: add no-op gettext() and eval_gettext() wrappers Ævar Arnfjörð Bjarmason
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=1301848953-31525-1-git-send-email-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.