Difference between revisions of "Extensions/website/Translating"
(→The Native-Lang representative) |
(→The Native-Lang representative) |
||
| Line 29: | Line 29: | ||
== The Native-Lang representative == | == The Native-Lang representative == | ||
| − | Each native lang community willing to have the extension website and descriptions in their 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. A first list is gathered in | + | Each native lang community willing to have the extension website and descriptions in their 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. A first list is gathered in this dedicated page [[Extensions/website/Translating/NL_Representative]] |
The website will have to provide some tools for them. | The website will have to provide some tools for them. | ||
Revision as of 10:20, 10 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/browser settings. Maybe some preferences may be stored (but not on the first version). The available languages are easilly accessible by country 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 volunteer on the site. They can then choose the extensions to translate for their language. Once the translations are submitted, an email is sent to the owner of the extension (see below).
At creation time, the extension owner should be able to provide translations in the language(s) they want. English should be highly recommended 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 their 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. A first list is gathered in this dedicated page Extensions/website/Translating/NL_Representative
The website will have to provide some tools for them.
- an email generated for each new translation needed (new or updated 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.
