Translation Team/Roadmap: Difference between revisions

(6 intermediate revisions by 2 users not shown)

Line 1:

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}

<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}}

* Create translation team

* Establish pootle server

* Determine how to translate wiki

* ....

==Proposals==

#Pootle will be used for source-code and activities.

#The Google Translation templates will be deployed as widely as possible on ~~hte~~ 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.

#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.

Line 21:

Line 18:

===Flow2 Wiki-templates===

Experience shows that the use of the wiki templates for translating pages in place on the wiki ~~suffer~~ from a number of significant problems.

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 ~~tha~~ nonetheless appears current.

#Pages fall out of synchrony, leading to bad information that nonetheless appears current.

#Localizers are not necessarily high-volume wiki-editors (whereas they do ~~congrergate~~ around Pootle and are generally familiar with it's use).

#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.

@@ Line 1: / Line 1: @@
-<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}
+<noinclude>{{TeamHeader|Translation Team}}[[Category:Roadmap]]</noinclude>
-{{TeamHeader|Translation Team}}</noinclude>
-{{TOCright}}
+==Status==
+{{Iframe|collapsed=|'''2011 September report:''' |http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg12368.html|900|1850|1}}
-* Create translation team
-* Establish pootle server
-* Determine how to translate wiki
-* ....
 ==Proposals==
 #Pootle will be used for source-code and activities.
-#The Google Translation templates will be deployed as widely as possible on hte 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.
+#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.
@@ Line 21: / Line 18: @@
 ===Flow2 Wiki-templates===
-Experience shows that the use of the wiki templates for translating pages in place on the wiki suffer from a number of significant problems.
+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 tha nonetheless appears current.
+#Pages fall out of synchrony, leading to bad information that nonetheless appears current.
-#Localizers are not necessarily high-volume wiki-editors (whereas they do congrergate around Pootle and are generally familiar with it's use).
+#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.