Re: improving our translations process
[email protected] (Philip Olson) Mon, 13 Apr 2009 20:51:36 -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]> |
> To manage translations, Fedora uses Transifex, a tool which I > co-develop. Transifex presents translators with statistics, allows > them to get the files and submit them back directly to the source > versioning system via an easy-to-use web interface. The actual > translation can be done either using a desktop application or a > web-based system. > > http://transifex.org/ > http://lwn.net/Articles/325311/ > https://translate.fedoraproject.org/tx/ > > I believe it's great to finally see PHP consider using the full power > of Docbook/i18n, which I suspect will have a big improvement on the > manual's translation completion and quality. Looks like an interesting option and definitely one to consider. If we go this route, would you be willing to help us set it up and/or help migrate at least translated content that's up to date? Or offer advice for such a transition? Do you feel transifex would work well for the PHP project? Most likely it would only be used for the PHP Manual but it's possible in the future other php.net projects could implement translations through it like phd, php-src errors, a few www.php.net elements... anything is possible I suppose. So yeah, something like transifex that's geared to manage multiple projects could find itself fully utilized here. Regards, Philip