Difference between revisions of "Extensions/website/Translating"
| Line 11: | Line 11: | ||
== Translating the website == | == Translating the website == | ||
| + | |||
| + | The user will have the correct language displayed based on the navigator language. 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 | ||
| + | |||
| + | |||
| + | |||
== Translating each desciption (living content) == | == Translating each desciption (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. | ||
When a translation is provided, an email is sent to the extension owner. | When a translation is provided, an email is sent to the extension owner. | ||
| − | == The Native-Lang | + | == 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. | 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 | + | The website will have to provide some tools for them. |
* an email generated for each new translations needed (new extension) | * an email generated for each new translations needed (new extension) | ||
Revision as of 15:24, 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 language. 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
Translating each desciption (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.
When a translation is provided, an email is sent to the extension owner.
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.
