On Fri, 15 Jun 2012 03:18:13 +0200 Roland Mainz wrote: > On Fri, May 25, 2012 at 9:19 PM, Glenn Fowler <[email protected]> wrote: > > On Fri, 25 May 2012 21:14:09 +0200 Lionel Cons wrote: > >> On 24 May 2012 22:40, Glenn Fowler <[email protected]> wrote: > >> > > >> > this is fixed in the next release > >> > thanks > > > >> Thank you. Did you merge Roland Mainz's localisation patch, too? > > > > not yet > > l18n is one of the items lurking in the todo list
> Erm... AFAIK this is "l10n" (=localisation). i18n yes, thanks for catching that -- if I repeat the mistake shame on me > (=internationalisation) is (restricted to Unix/Linux application) more > or less about that application can process characters outside the > ASCII range. > > there are some curfty message catalog generation scripts that need to be > > dusted off and re-tested > > including the parts that reap l18n strings from scripts. > Erm... this can be split into three pieces which can be done in parallel: > 1. Localise scripts, e.g. replace "..." string literals with $"..." > 2. Generate catalogs for the "C" locale using $ ksh93 -D scriptname > ... # and put them under $INSTALLROOT in the right place > 3. Create toolchain/scripts which fetches the C strings from these > catalogs and feeds them to something like Google translate (if no > manual translation is available) > Glenn: I can easily do [1] if you accept patches for that (my previous > one for tar.sh needs to be updated anyway... and there is plenty of > other script stuff which needs to be localised in ast-open) ... before you do that let me make sure the l10n machinery works so that you can test the "..." => $"..." patches before submitting them and so you can test that the l10n stuff works outside of the gsf magic environment I'll try to look at this before my vacation 1st 2 weeks in july _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
