From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 0/6] Gettext poison rework
Date: Fri, 24 Aug 2012 12:43:00 +0700 [thread overview]
Message-ID: <1345786986-10826-1-git-send-email-pclouds@gmail.com> (raw)
Still WIP but I'm getting closer. I dropped test-poisongen and started
to use podebug [2] instead. Less code in git. podebug does not preserve
shell variables yet. I'll follow that up at upstream [1].
With this series, if you have translation toolkit installed, you could
do
make pseudo-locale L=<your language code>
make GETTEXT_POISON=$LANG test
podebug supports a few way of rewriting translations. Currently
"unicode" is used but you can change it via PODEBUG_OPTS
t9001 is not happy with $LANG != C though. May need to add some
prereq there.
[1] http://bugs.locamotion.org/show_bug.cgi?id=2450
[2] http://translate.sourceforge.net/wiki/toolkit/podebug
Nguyễn Thái Ngọc Duy (6):
Makefile: do not mark strings for l10n from test programs
Makefile: recreate git.pot if *.sh or *.perl changes
Replace gettext poison implementation with pseudotranslation
generation
Initialize gettext for test programs that may use it
Support logging unmarked strings
test-parse-options: mark parseopt help strings for pseudotranslation
.gitignore | 1 +
Makefile | 48 +++++++++++++++++++++---------------
gettext.c | 10 --------
gettext.h | 10 +-------
git-sh-i18n.sh | 14 -----------
po/.gitignore | 1 +
po/README | 15 +++++------
t/.gitignore | 1 +
t/lib-gettext.sh | 7 +++++-
t/t0200-gettext-basic.sh | 1 +
t/t0205-gettext-poison.sh | 36 ---------------------------
t/test-lib.sh | 2 +-
test-date.c | 1 +
test-delta.c | 1 +
test-dump-cache-tree.c | 5 +++-
test-index-version.c | 1 +
test-match-trees.c | 1 +
test-mergesort.c | 1 +
test-parse-options.c | 63 ++++++++++++++++++++++++-----------------------
test-path-utils.c | 1 +
test-revision-walking.c | 1 +
test-scrap-cache-tree.c | 4 ++-
test-sha1.c | 1 +
test-subprocess.c | 1 +
wrap-for-bin.sh | 16 +++++++++++-
25 files changed, 111 insertions(+), 132 deletions(-)
delete mode 100755 t/t0205-gettext-poison.sh
--
1.7.12.rc2
next reply other threads:[~2012-08-24 5:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 5:43 Nguyễn Thái Ngọc Duy [this message]
2012-08-24 5:43 ` [PATCH 1/6] Makefile: do not mark strings for l10n from test programs Nguyễn Thái Ngọc Duy
2012-08-24 5:43 ` [PATCH 2/6] Makefile: recreate git.pot if *.sh or *.perl changes Nguyễn Thái Ngọc Duy
2012-08-24 5:43 ` [PATCH 3/6] Replace gettext poison implementation with pseudotranslation generation Nguyễn Thái Ngọc Duy
2012-08-24 5:43 ` [PATCH 4/6] Initialize gettext for test programs that may use it Nguyễn Thái Ngọc Duy
2012-08-24 5:43 ` [PATCH 5/6] Support logging unmarked strings Nguyễn Thái Ngọc Duy
2012-08-24 5:43 ` [PATCH 6/6] test-parse-options: mark parseopt help strings for pseudotranslation Nguyễn Thái Ngọc Duy
2012-08-24 8:51 ` [PATCH 0/6] Gettext poison rework Ævar Arnfjörð Bjarmason
2012-08-24 10:54 ` Nguyen Thai Ngoc Duy
2012-08-24 16:02 ` Junio C Hamano
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=1345786986-10826-1-git-send-email-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).