Ã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.
--
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