Re: [PATCH] Support generate poison .mo files for testing

[Nguyen Thai Ngoc Duy <pclouds@gmail.com>]

On Wed, Aug 22, 2012 at 6:13 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes:
>
>> test-poisongen does a similar job to gettext poison feature except
>> that it does it at build time. Gibberish .mo files are generated for
>> all supported langauges and put in po/build/poison-locale. Target
>> "poison-locale" is for this.
>
> What is the significance of this locale being "Gibberish"?
> Currently, for any string, we give "### gettext poison ###" or
> something but the only thing we care about in the poison mode is
> that it is different from the message id, no?  I was wondering if
> these phony translations can be something simple like "Add QQ at the
> beginning of the message id string" and still can catch mistakenly
> marked messages that come from the plumbing layer, or something.

I'm gradually getting there, partly thanks to your question about
grepping "tracked" in another thread. This patch does not really
generate random strings. It repeats the pattern "* gettext poison *"
for evey character that can be replaced. But a better way could be
replacing "tracked" with "t r a c k e d". We know the rule so we can
recreate the that string from "tracked" in test_i18n*. Or reverse the
upper/lower case, whichever is easier for the recreation by test_i18n*

>>  mode change 100644 => 100755 t/test-lib.sh
>>  create mode 100644 test-poisongen.c
>>  mode change 100644 => 100755 wrap-for-bin.sh
>
> Thanks.  I suspect two mode changes weren't intentional?

It's an emacs hook gone bad.
-- 
Duy