Difference between revisions of "Extensions/website/Translating"
| Line 13: | Line 13: | ||
== Translating each desciption (living content) == | == Translating each desciption (living content) == | ||
| + | |||
| + | |||
| + | |||
| + | When a translation is provided, an email is sent to the extension owner. | ||
== The Native-Lang correspondant == | == The Native-Lang correspondant == | ||
| Line 23: | Line 27: | ||
* some basic lists (non-translated extensions, waiting for review) | * some basic lists (non-translated extensions, waiting for review) | ||
| − | This representative will be helped by volunteers that identify on the extension website and | + | This representative will be helped by volunteers that identify on the extension website and provide translations for targeted extension. |
Revision as of 15:16, 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
Translating each desciption (living content)
When a translation is provided, an email is sent to the extension owner.
The Native-Lang correspondant
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 these workers.
- 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.
