Re: Status of doc migration to Git
| From: | Dean Sas | Date: | Fri, 04 Apr 2014 21:51:00 +0000 |
| Subject: | Re: Status of doc migration to Git | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969384924@lists.php.net to get a copy of this message | ||
On Fri, Apr 4, 2014 at 12:57 AM, Philip Olson <philip@roshambo.org> wrote:
> I’m not sure how best to handle the translation process but
> simplifying it (e.g., not requiring us to track the number
> of revisions) sounds okay to me. We don’t have to keep the
> exact system we have, a system that was designed with CVS.
Gnome, Ubuntu and others use xml2po [0]. It takes docbook and spits
out a .pot file, the same as gettext translations. You can then run
xml2po again with the translated .po file to create translated
docbook.
When the English changes you re-run xml2po and use the gettext tools
to merge the new strings into the existing translation files.
An advantage is that if the English changes and the translators don't
keep up, the English strings will be in the translated version, rather
than the information being totally absent.
Open source translators are used to using gettext systems to translate
and there are various GUIs as well as web editors like transifex and
launchpad which understand them.
I don't really know much about the current translation system, so I
may have overlooked reasons which make this unsuitable.
Regards,
Dean
[0] https://git.gnome.org/browse/gnome-doc-utils/tree/xml2po/README.in