From: Ævar Arnfjörð Bjarmason Date: Sat, 12 Feb 2011 20:55:46 GMT Subject: Re: How you can translate things now, and a plan for the i18n series going forward Message-ID: In-Reply-To: <7vipwpxbam.fsf@alter.siamese.dyndns.org> On Sat, Feb 12, 2011 at 21:12, Junio C Hamano wrote: > Ævar Arnfjörð Bjarmason 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.