On Sat, Apr 11, 2009 at 8:32 PM, Philip Olson <phi...@roshambo.org> wrote: > 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. > > > 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.
PO files are considered a standard way of doing translations, and quite a few tools are available which provide good support for both translators and developers. It allows the translators to work more efficiently by translating exactly what is needed, and also allows them to detect easily when the source file has been changed and update their translations. 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. -δ -- Dimitris Glezos Jabber ID: gle...@jabber.org, GPG: 0xA5A04C3B http://dimitris.glezos.com/ "He who gives up functionality for ease of use loses both and deserves neither." (Anonymous) --
