By qgil on

A couple of questions:

How far is Drupal from using/importing/exporting PO files for publishing content in several languages?

How far is Drupal from having a revision control system showing to translators what changed in the original English pages and what needs updating in the translations?

Note that we are talking about translating content, not the Drupal interface strings.

We are looking for the right CMS for www.gnome.org, a subsite explaining all the basics about the GNOME project. We have a list of CMS requirements and a critical point is i18n. We are evaluating several possibilities and we have Drupal as a candidate (feel free to add your comments).

We want this subsite translated into the languages supported by GNOME. We have now 42 locales supported, plus 17 partially supported. The GNOME Translation Project involves dozens of teams sharing coordination, methodologies and translation tools. Our system works, and we want the CMS to adapt to it. PO files and revision control are a must.

Since PO files and revision control are standard elements of i18n in most major free software projects, we believe that a CMS providing these features would make a difference.

Thank you for your help.

Comments

rkerr’s picture

rkerr commented

Since no one has yet responded here, I suppose handling translations of content with PO files hasn't occurred to anyone using Drupal before. I think some people have previously used prefixed tables, or the like and done everything strictly through the standard Drupal interface instead of importing pre-translated files.

A PO importer for content translations (and tracking of those translations) could certainly be written as a module for Drupal. I would be interested in knowing what your current proccess and PO files look like. :)