On Thu, Oct 14, 2010 at 21:50, Jon Seymour <jon.seymour@xxxxxxxxx> wrote:
> On Fri, Oct 15, 2010 at 8:18 AM, Ãvar ArnfjÃrà Bjarmason
> <avarab@xxxxxxxxx> wrote:
>> On Thu, Oct 14, 2010 at 20:54, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote:
>>> Ãvar ArnfjÃrà Bjarmason wrote:
>> So what I've tried to do to make this acceptable for inclusion in core
>> is to make this whole thing a no-op unless it's explicitly
>> requested.
>>
> I agree with Jonathan that there might be some value to clearly
> delineating the i18n infrastructure from the application of it to the
> rest of the code base.The i18n infrastructure should be, relatively
> speaking, less invasive than the application of it throughout the code
> base.
>
> It would be good for Junio (I presume) to have the option to integrate
> the infrastructure in one hit, but allow the application of it to be
> deferred, perhaps on a subject-area by subject-area basis.
It already is pretty much separate internally. To get only the
infrastructure you pull the series and omit the "gettextize"
patches. There is some slight tangling up e.g. here:
6da9243 gettext tests: skip lib-gettext.sh tests under GETTEXT_POISON
234ddee gettextize: git-init basic messages
b161357 gettextize: git-init "Initialized [...] repository" message
3ad3f9f gettext tests: test if $VERSION exists before using it
1f56190 gettext tests: add detection for is_IS.ISO-8859-1 locale
5f24f25 gettext tests: test message re-encoding under Shell
ec31cc6 gettext tests: test re-encoding with a UTF-8 msgid under Shell
45e8a56 gettext tests: mark a test message as not needing translation
c9db9aa po/is.po: add Icelandic translation
83beb97 gettext tests: test message re-encoding under C
Where the tests I'm adding depend on an earlier "gettextize"
patch. That can easily be split up if there's demand for it. But so
far nobody has asked so I haven't done it.
--
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