Re: improving our translations process

[email protected] (Philip Olson) Sat, 11 Apr 2009 10:32:23 -0700

Newsgroups	php.doc,php.doc.ar,php.doc.bg,php.doc.cs,php.doc.da,php.doc.de,php.doc.es,php.doc.el,php.doc.fa,php.doc.fi,php.doc.fr,php.doc.he,php.doc.hk,php.doc.hu,php.doc.it,php.doc.ja,php.doc.kr,php.doc.nl,php.doc.pl,php.doc.pt,php.doc.pt-br,php.doc.ro,php.doc.ru,php.doc.sk,php.doc.sl,php.doc.sv,php.doc.tr,php.doc.tw,php.doc.zh,php.doc.no,php.doc.se
Message-ID	<[email protected]>

Everyone,

The question is not whether we move the documentation repositories to  
a new version control system (like svn), because the entire php.net  
will do that. The question here is how to better manage the  
translation process and ideally come up with a solution before that  
move. Well, we must, because the change forces us to.

One option is to use gettext. This could mean English is in DocBook  
and translations use po files that are generated and managed from that  
DocBook. Please think about this and other options. This would involve  
using CAT and other modern methods so have a look:

   - CAT: http://en.wikipedia.org/wiki/Computer-assisted_translation

The po (gettext) option seems to offer the most tools and flexibility,  
and other projects in the Open Source community (like KDE, Ubuntu) use  
it. I may sound set in using po but am not and am only researching  
ideas. Please discuss this and other ideas. And, volunteers are needed  
to help migrate to whatever new system we choose.

Regards,
Philip