On Sat, Feb 12, 2011 at 21:12, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> Ãvar ArnfjÃrà Bjarmason <avarab@xxxxxxxxx> writes:
>
>> Hi both. I've been on a hiatus from Git development, so I haven't
>> picked up ab/i18n again, but I still plan to and to get it included in
>> Git.
>
> Thanks.
>
>> Â Â *** TODO Introduce a skeleton no-op gettext, just the
>> infrastructure minus the interesting stuff
>>
>> Â Â Â Â I.e. just add:
>>
>> Â Â Â Â Â Â #define N_(s) (s)
>> Â Â Â Â Â Â #define _(s) (s)
>>
>> Â Â *** TODO Add no-op C gettextize patches
>>
>> Â Â Â Â This will change "foo" to _("foo") everywhere, but will be a no-op
>> Â Â Â Â due to it being macroed out.
>
> It would be best to get this as early as possible while not many topics
> are in 'next'; it is preferrable if we can rebase other topics in 'pu' on
> top of the result of this step.
>
>> Â Â *** TODO Add no-op Shell/Perl gettextize patches
>>
>> Â Â Â Â Due to the nature of these languages these can't be macroed out,
>> Â Â Â Â but it's still easy to have a no-op wrapper function.
>
> Yes. ÂAfter the above two steps are done, we can pretty much independently
> advance and tweak i18n topic from other changes.
>
>> Â Â *** TODO Add po/README etc.
>>
>> Â Â Â Â The documentation about how to add translations etc.
>>
>> Â Â *** TODO Add translations
>>
>> Â Â Â Â Add the po/*.po files. Since we have no-op translations everywhere
>> Â Â Â Â we can translate git with xgettext + po editing, even though the
>> Â Â Â Â translations aren't being used yet.
>>
>> Â Â *** TODO Introduce the real gettext in a later patch + tests
>>
>> Â Â Â Â Once the rest is all in this will be a much smaller change.
>
> The last two could probably be swapped, but I think we are on the same
> page as to the overall steps and direction.
Right, good to hear we're on the same page.
I'll be doing a Perl release on the 20th, and I'm traveling around,
but I hope to get around to this sooner rather than later.
--
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