Translation Team/Roadmap - Revision history

FGrose at 05:50, 11 September 2011

2011-09-11T05:50:14Z

← Older revision		Revision as of 01:50, 11 September 2011
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==		==Proposals==

Cjl: moved Walter is a wanker 14/Roadmap to Translation Team/Roadmap over redirect: revert

2010-02-25T00:00:44Z

moved Walter is a wanker 14/Roadmap to Translation Team/Roadmap over redirect: revert

← Older revision	Revision as of 20:00, 24 February 2010
(No difference)

Faggot: moved Translation Team/Roadmap to Walter is a wanker 14/Roadmap: Walter is a wanker

2010-02-24T23:53:11Z

moved Translation Team/Roadmap to Walter is a wanker 14/Roadmap: Walter is a wanker

← Older revision	Revision as of 19:53, 24 February 2010
(No difference)

Cjl: /* Flow2 Wiki-templates */

2009-04-06T18:34:08Z

Flow2 Wiki-templates

← Older revision		Revision as of 14:34, 6 April 2009
Line 24:		Line 24:
	#Pages fall out of synchrony, leading to bad information that 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 congregate 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.

Cjl: /* Flow2 Wiki-templates */

2009-04-06T18:32:34Z

Flow2 Wiki-templates

← Older revision		Revision as of 14:32, 6 April 2009
Line 21:		Line 21:

	===Flow2 Wiki-templates===		===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 that 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 congregate 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).

Cjl: /* Flow2 Wiki-templates */

2009-04-06T18:31:09Z

Flow2 Wiki-templates

← Older revision		Revision as of 14:31, 6 April 2009
Line 22:		Line 22:
	===Flow2 Wiki-templates===		===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 suffer 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).

Cjl at 18:30, 6 April 2009

2009-04-06T18:30:23Z

← Older revision		Revision as of 14:30, 6 April 2009
Line 11:		Line 11:

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

Cjl at 18:29, 6 April 2009

2009-04-06T18:29:35Z

← Older revision		Revision as of 14:29, 6 April 2009
Line 10:		Line 10:
	==Proposals==		==Proposals==

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

	[[Image:TranslationFlow1.PNG]]		[[Image:TranslationFlow1.PNG]]

			===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.
			#Pages fall out of synchrony, leading to bad information tha 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).

FGrose at 18:14, 6 April 2009

2009-04-06T18:14:08Z

← Older revision		Revision as of 14:14, 6 April 2009
Line 7:		Line 7:
	* Determine how to translate wiki		* Determine how to translate wiki
	* ....		* ....

			==Proposals==

			===Flow1===

			[[Image:TranslationFlow1.PNG]]

Dfarning: add web page translation

2009-04-04T22:24:18Z

add web page translation

← Older revision		Revision as of 18:24, 4 April 2009
Line 5:		Line 5:
	* Create translation team		* Create translation team
	* Establish pootle server		* Establish pootle server
			* Determine how to translate wiki
	* ....		* ....