From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH 0/6] Gettext poison rework
Date: Fri, 24 Aug 2012 10:51:45 +0200 [thread overview]
Message-ID: <CACBZZX7V3A02sPQex4zpBE8Tkmc2d037tJBfhn-6DeK_MwY2Hw@mail.gmail.com> (raw)
In-Reply-To: <1345786986-10826-1-git-send-email-pclouds@gmail.com>
On Fri, Aug 24, 2012 at 7:43 AM, Nguyễn Thái Ngọc Duy <pclouds@gmail.com> wrote:
> 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
The reason I didn't do something like this to begin with is that
gettext/glibc doesn't have support for fake locales, so you'd have to
appropriate a real one for tests. It's good to see you poking the
gettext mailing list about adding support far thot.
But something like podebug gets around that quite nicely, so we can
still have the testing the poison stuff was intended for, without the
complexity of supporting it throughout all our i18n code.
next prev parent reply other threads:[~2012-08-24 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 5:43 [PATCH 0/6] Gettext poison rework Nguyễn Thái Ngọc Duy
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 ` Ævar Arnfjörð Bjarmason [this message]
2012-08-24 10:54 ` [PATCH 0/6] Gettext poison rework 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=CACBZZX7V3A02sPQex4zpBE8Tkmc2d037tJBfhn-6DeK_MwY2Hw@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@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).