[Localization] Gtranslator on the xo
samy boutayeb
s.boutayeb at free.fr
Thu Jun 10 11:27:16 EDT 2010
Hola Sebastian,
Glad to see that your project is avancing.
Le jeudi 10 juin 2010 à 10:02 -0500, Sebastian Silva a écrit :
> Hello everybody,
> We are finally about to start a translation event here in PUNO,
> high in the Andes Mountains, in front of the Titicaca lake.
>
> Our plan is to work on a Glossary with the most common terms,
> then distribute printed lists of strings so that people can focus on
> the translation. This is because we may not have enough computers
> for translators and because many of them may not feel comfortable
> with the computer (yet).
>
> I am still wondering what version to translate as I´d like to
> translate
> Sugar 0.88 in hopes of including the translation in the new images
> that Bernie and ParaguayEduca team are preparing. But I don´t see
> a String Freeze for this - where should I collect these .po files?
>
For quechua:
http://translate.sugarlabs.org/qu/
For aymara:
* Language page:
http://translate.sugarlabs.org/ay/
* Open the project pages (for example the "Fructose" page):
http://translate.sugarlabs.org/ay/fructose/review.html
* Download the zip archive with the xo files
http://translate.sugarlabs.org/ay/fructose/export/zip
* Export the xo files to a csv (comma separated value) with
"po2csv" (convert Gettext PO localization files to Comma-Separated Value
(.csv) files see: http://translate.sourceforge.net/wiki/toolkit/po2csv
for examples and usage instructions)
* Import the csv files to a spreadsheet document (Office Calc)
* Print your pages
* Start ranslating ;-)
Hasta luego
Samy
> I´m created a ticket [1] to have privileges for these languages.
> Also I´ll be in #olpc-pootle tomorrow in case we have further
> questions.
>
> [1] http://bugs.sugarlabs.org/ticket/2038
>
> Thanks for all your help!
> Sebastian
>
> 2009/9/23 <s.boutayeb at free.fr>
> Hi Chris,
>
> I wrote a small description (sort of) of the workflow here:
>
> http://olpc-france.org/blog/2009/08/traduire-sugar-le-xo/
>
> The examples show that:
> - the use of an offline tool is feasible
> - the XO can be uses as an localization platform, especially
> where no other PC
> is available
> - the use of 3 languages is feasible too
>
> As for creating a new language pair (that is aymara>spanish or
> quechua>spanish),
> it's possible using po2swap:
>
> Let's see what "poswap --help" says:
>
> --------------------------------------------
> Usage: poswap [--version] [-h|--help] [--manpage] [--progress
> PROGRESS]
> [--errorlevel ERRORLEVEL] [-i|--input] INPUT [-x|--exclude
> EXCLUDE]
> [-o|--output] OUTPUT [-t|--template TEMPLATE]
>
> Builds a new translation file with the target of the input
> language as source
> language. Ensure that the two po files correspond 100% to the
> same pot file
> before using this. To translate Kurdish (ku) through French::
> po2swap -i
> fr/ -t ku -o fr-ku To convert the fr-ku files back to en-ku::
> po2swap
> --reverse -i fr/ -t fr-ku -o en-ku See:
> http://translate.sourceforge.net/wiki/toolkit/poswap for
> further examples and
> usage instructions
> -------------------------------------------
> Hope this helps
>
> Saludos/Best regards
>
> Samy
>
>
> Selon Chris Leonard <cjlhomeaddress at gmail.com>:
>
>
> > Sebastian,
> >
> > Although it would certainly take some additional
> administrative
> > coordination, I've always wondered whether it might make
> sense to add a few
> > steps to an off-line translation workflow for indigineous
> South American
> > languages (Quechua, Aymara, etc.) where the original strings
> are first
> > rendered in Spanish and later switched back to English. The
> reason being
> > that there may be more people for whom Spanish-to-Quechua
> translation is
> > feasible than English-to-Quechua (probably being discussed
> in Spanish).
> >
> > Using the Translation Toolkit poswap function, first take
> the completed
> > lang-es PO files and swap the msgid into Spanish, perform
> the Quechua
> > localization using an off-line tool, and then (before
> submission and
> > commitment to Pootle) swap the msgids back into English to
> create a properly
> > formatted PO file.
> >
> > http://translate.sourceforge.net/wiki/toolkit/poswap
> >
> > I have not played around with this part of the Translate
> Toolkit, but it
> > certainly looks promising. The fact tah tour Spanish
> Localization is very
> > near completion also helps a great deal. Just a thought.
> >
> > cjl
> >
> > On Sat, Aug 22, 2009 at 6:42 AM, <s.boutayeb at free.fr> wrote:
> >
> > > Hola Sebastian,
> > >
> > > Selon Sebastian Silva <sebastian at fuentelibre.org>:
> > >
> > > > I'm very interested in trying this and working on a good
> workflow,
> > > > hopefully one where I can build the translated sugar
> instantly and
> > > > let the translator experiment. Once we have this
> workflow, I'll make
> > > > a big invite for Quechua speakers.
> > > > I think this is a good way to go, how do we integrate
> with the pootle
> > > > then?
> > > >
> > > > I'll investigate, lets share what we find.
> > > >
> > > > Thank you
> > > >
> > > > Sebastian
> > >
> > > After installing gtranslator on a XO with Sugar 0.84.2, I
> tried the
> > > installation
> > > of virtaal and Translate Toolkit
> > > (http://sourceforge.net/projects/translate/files/ ) but
> didn't succeed in
> > > running them on the XO.
> > >
> > > This said, those tools can be used on standard PC too.
> > >
> > > With an offline translation tool (gtranslator or another
> one), the workflow
> > > could be as following:
> > >
> > > - download a .po file from the pootle server.
> > > - open it with the translation tool and update the
> translation
> > > - compile the .po files into binary .mo files with msgfmt
> > > - copy the .mo file in the respective directory: the .mo
> files are stored
> > > in
> > > /usr/share/locale/<your locale>/LC_MESSAGES/ with the name
> of the original
> > > file
> > > + the extension .mo (e.g. labyrinth.mo is the compiled
> file for
> > > labyrinth.po)
> > > or, alternatively, in the /home/olpc/Activities/<Name of
> the
> > > Activity>/locale/<Your locale>/LC_MESSAGES/ , with the
> name (for example
> > > "org.gnome.Labyrinth.mo".
> > > - test your activity with your translation
> > > - correct the required strings with your translation tool
> > > - upload the corrected .po file on the Pootle server
> > >
> > > Comments appreciated
> > >
> > > Muy atentamente/Best regards
> > >
> > > Samy
> > >
> > > >
> > > > 2009/8/21 <s.boutayeb at free.fr>
> > > >
> > > > > Hi all,
> > > > >
> > > > > In some/many cases, the connectivity may be an issue
> for localization
> > > teams
> > > > > (as
> > > > > it's the case for our deployment in madagascar (see:
> > > > > http://olpc-france.org/blog/category/nosy-komba/).
> > > > >
> > > > > So, one potential alternative is to use an offline
> translaton tool.
> > > > >
> > > > > I have tested a bit the installation and the use of
> the gtranslator
> > > > > application
> > > > > (http://gtranslator.sourceforge.net/). The test
> platform is an xo 1
> > > with
> > > > > SoaS-XO
> > > > > and Sugar 0.84.2.
> > > > >
> > > > > See a screenshot here:
> > > > >
> > > > >
> http://olpc-france.org/wiki/index.php?title=Image:Gtranslator1.png
> > > > >
> > > > > Could anyone confirm the feasability of the worflow?
> Especially with
> > > older
> > > > > builds used in the wild?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Samy
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Localization mailing list
> > > > > Localization at lists.laptop.org
> > > > > http://lists.laptop.org/listinfo/localization
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sebastian Silva
> > > > Laboratorios FuenteLibre
> > > > http://blog.sebastiansilva.com/
> > > >
> > >
> > >
> > > _______________________________________________
> > > Localization mailing list
> > > Localization at lists.laptop.org
> > > http://lists.laptop.org/listinfo/localization
> > >
> >
>
>
>
>
>
>
> --
> Sebastian Silva
> http://somosazucar.org/
> "Te imaginas si te pudieran enseñar sólo a leer pero no a escribir??"
More information about the Localization
mailing list