Difference between revisions of "Translation Team/Roadmap"
Jump to navigation
Jump to search
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <noinclude> | + | <noinclude>{{TeamHeader|Translation Team}}[[Category:Roadmap]]</noinclude> |
| − | {{TeamHeader|Translation Team}}</noinclude> | + | |
| − | {{ | + | ==Status== |
| + | {{Iframe|collapsed=|'''2011 September report:''' |http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg12368.html|900|1850|1}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
==Proposals== | ==Proposals== | ||
#Pootle will be used for source-code and activities. | #Pootle will be used for source-code and activities. | ||
| − | #The Google Translation templates will be deployed as widely as possible on | + | #The Google Translation templates will be deployed as widely as possible on the wiki. While these machine translations provide a limited (but significant) number of languages, they have the advantage of always be as current as the wiki page itself and even with the problems inherent in the quality of machine translations, they are generally *good enough* for basic comprehension. |
#A certain (small) subset of pages truly require a careful human translation because they contain instructions for installing or downloading our tools and the consequences of getting it wrong are very high or likely to discourage use of Sugar if the instructions are not clear and accessible. | #A certain (small) subset of pages truly require a careful human translation because they contain instructions for installing or downloading our tools and the consequences of getting it wrong are very high or likely to discourage use of Sugar if the instructions are not clear and accessible. | ||
| Line 21: | Line 18: | ||
===Flow2 Wiki-templates=== | ===Flow2 Wiki-templates=== | ||
| − | Experience shows that the use of the wiki templates for translating pages in place on the wiki | + | Experience shows that the use of the wiki templates for translating pages in place on the wiki suffers from a number of significant problems. |
| − | #Pages fall out of synchrony, leading to bad information | + | #Pages fall out of synchrony, leading to bad information that nonetheless appears current. |
| − | #Localizers are not necessarily high-volume wiki-editors (whereas they do | + | #Localizers are not necessarily high-volume wiki-editors (whereas they do congregate around Pootle and are generally familiar with it's use). |
| + | #The existing templates (e.g. those currently employed on wiki.l.o) are very difficult to understand and use. | ||
Latest revision as of 01:50, 11 September 2011
Status
2011 September report:
Proposals
- Pootle will be used for source-code and activities.
- The Google Translation templates will be deployed as widely as possible on the wiki. While these machine translations provide a limited (but significant) number of languages, they have the advantage of always be as current as the wiki page itself and even with the problems inherent in the quality of machine translations, they are generally *good enough* for basic comprehension.
- A certain (small) subset of pages truly require a careful human translation because they contain instructions for installing or downloading our tools and the consequences of getting it wrong are very high or likely to discourage use of Sugar if the instructions are not clear and accessible.
For these "high-value" pages, providing a means for high-quality human translations is worth the effort. There are several possible approaches.
Flow1 static HTML and Pootle
Flow2 Wiki-templates
Experience shows that the use of the wiki templates for translating pages in place on the wiki suffers from a number of significant problems.
- Pages fall out of synchrony, leading to bad information that nonetheless appears current.
- Localizers are not necessarily high-volume wiki-editors (whereas they do congregate around Pootle and are generally familiar with it's use).
- The existing templates (e.g. those currently employed on wiki.l.o) are very difficult to understand and use.