Looking at how the locale.module works now, e.a. every site owner is doing their own translating. Sharing these translations is not a very well supported process. How about extending the locale.module to streamline translation more. One should be able to devide translations in catagories, e.a. this translation was for drupal 4.2.0, for module X v.4.3.0 etc. Then other drupal and module users could download (import) translated module or `drupals` from the main drupal site per language and per module (or also an extra package with all standard modules).

An export button would export stuff, e.a.
export: node.module -> v.4.2.0 -> translated strings -> v1.0
or
export: user.module -> v.4.2.0 -> translated strings -> v1.0
which others can then ..import?
The v1.0 would resemble a translation version.

When you import stuff, you get your specific modules up to date in your languages.

CommentFileSizeAuthor
#1 common-plural.patch782 byteskilles@www.drop.org
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

killes@www.drop.org’s picture

Title: import and export translations » import and export translations using PO files
Version: » master
Assigned: Unassigned » killes@www.drop.org
FileSize
782 bytes

We have decided to use PO files to facilitate sharing of translations. They are a well established quasi-standard in the free software world.

Jacobo Tarrio has provided PO fie parsers, I will incorporate them in a new locale.module.

As a side benefit the PO file format supports plural forms for languages with more than one plural form. A patch for format_plural is attached. It will be only usable with the new locale module.

killes@www.drop.org’s picture

new locale is in core.

Anonymous’s picture