Difference between revisions of "Extensions/website/Translating"

Revision as of 15:39, 9 September 2007

The website and its content needs to be translated.

There are 3 parts to be worked on

• the website itself
• the extension description
• the extension itself

If tools can be built to address point 3, we only will work the first 2 points

Translating the website

The user will have the correct language displayed based on the navigator settings. Maybe some preferences may be stored (but not on the first version). The available languages are easilly accessible by contry flags or better a dropdown language list.

The translation mechanism should join the l10n project if possible

If a part is not translated, english is displayed.

Translating each desciption and living content

The drupal framework will have to be used. The process has to be light so it can be done by non-technical volunteers that identify on the site. They can choose nedded transaltions for their languages.

At creation time, extensions owner should be able to provide translations in tha language they want. English should be highly recommanded if not mandatory

When a translation is provided, an email is sent to the extension owner to inform him.

The categories/tags will also be translatable

The Native-Lang representative

Each native lang community willing to have the extension website and descriptions in its language will have to nominate a representative that will be the bridge between the translators and the extensions project. This representative will have to check that the submitted translations are correct and not offending.

The website will have to provide some tools for them.

• an email generated for each new translations needed (new extension)
• some basic lists (non-translated extensions, waiting for review)

This representative will be helped by volunteers that identify on the extension website and provide translations for targeted extension.