Traslation tools

[Davi Leal]

Antenore Gatta <address@hidden>:
> Cool! I love gettext!

It is the best solution I have seen. I agree with you.


> I'm traslating the po file, I'm using the Spanish one as template. To avoid
> unusefull trash in the cvs (I don't know when I'll be able to update it),

Take the needed time.

> I'll send the po file directly to this mailing list if you are agree, or
> directly to you (better I think).

It is better send it directly to the mailing list to others can follow
the work that is been realized, and so everybody can advise at any
time. All kind of mails should be sent to the list.


> Give me some days (it's really boring, you know).

I know, I know :)   It takes a lot of time.

I like this introduction to gettext.
 http://fplanque.net/Blog/devblog/2003/08/18/introducing_gettext_and_po_files
 http://www.poedit.org/screenshots.php

The tool 'poedit' can parse PHP source but I think it can not the
smarty templates we use. Anyway, I will try to modify the smarty tool
tsmarty2c.php to parse both translation tags we are using:

 {t}string to translate{/t}

 {'string to translate'|gettext}

I have not used xgettext to extract the strings. I have done it by
hand.  I hope we will be able to use an automatic system to extract
and update the strings from the source code: PHP and smarty templates.


> See you soon!

I am looking forward for getting this project in production and hosted
at the FSF.

Davi