Re: [PATCH 03/65] i18n: archive: mark parseopt strings for translation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 7, 2012 at 7:41 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote:
> Nguyen Thai Ngoc Duy wrote:
>
>> No changes to the series then. Junio, pu material perhaps? The
>> breaking gettext poison thing is different and I plan to kill gettext
>> poison soon (whether i succeed is another question of course).
>
> If you mean to kill it by replacing it with a facility to run tests in
> another locale, wouldn't all these testsuite bugs still be testsuite
> bugs?

They still are and should be fixed when the new facility comes, so
there's no point fixing them now. I played with the poison .po
generation a bit and started to use libgettext-po, which would give us
more control over reading/writing .po. We could even perform
git-specific checks on po files..

The said plan is to build .mo for $LANG in po/build/poison-locale
(po/build/locale remains good translation) and add a switch to make
the test suite use poison-locale instead. Long term I'd like to switch
to poison locale by default, unless LANG is C, maybe with an option to
run with real .mo files.
-- 
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]