Translation Team/FAQ - Revision history

FGrose: /* I have trouble translating the English to my language. Can I see translations in another language? */ shorten section title

2014-02-06T01:35:56Z

I have trouble translating the English to my language. Can I see translations in another language?: shorten section title

← Older revision		Revision as of 21:35, 5 February 2014
Line 90:		Line 90:
	:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.		:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.

	==== ~~I have trouble translating the English to my language.~~ Can I see translations in another language? ====		==== Can I see translations in another language? ====
	: Pootle can show you the translations in an third language while you translate. In order to see that, select the alternate language from your options page (once you have logged in).		: Pootle can show you the translations in an third language while you translate. In order to see that, select the alternate language from your options page (once you have logged in).

Cjl: /* How do I add a project to be translated ? */

2010-03-30T17:20:30Z

How do I add a project to be translated ?

← Older revision		Revision as of 13:20, 30 March 2010
Line 122:		Line 122:

	Basic steps for git.sugarlabs.org hosted projects:		Basic steps for git.sugarlabs.org hosted projects:
	#) /po/ directory set up in top-level of git repo containing the .pot file produced by gettext.		# /po/ directory set up in top-level of git repo containing the .pot file produced by gettext.
	#) user:pootle granted commit priv to the repo		# user:pootle granted commit priv to the repo
	#)Ticket opened in bugs.sugarlabs.org requesting hosting of project PO files in Pootle, please provide link to git repo.		# Ticket opened in bugs.sugarlabs.org requesting hosting of project PO files in Pootle, please provide link to git repo.

	==== How do I start a translation team for my language ?====		==== How do I start a translation team for my language ?====

Cjl: /* How do I add a project to be translated ? */

2010-03-30T17:19:57Z

How do I add a project to be translated ?

← Older revision		Revision as of 13:19, 30 March 2010
Line 120:		Line 120:
	==== How do I add a project to be translated ? ====		==== How do I add a project to be translated ? ====
	: If you are using the GIT services on git.sugarlabs.org, just file a ticket at http://dev.sugarlabs.org under the component localization, mentioning the name of the GIT repository. If your project is hosted somewhere else, please file a ticket detailing how to access your project's version control setup, and we'll try to figure out a way how to best integrate your project's translation related files.		: If you are using the GIT services on git.sugarlabs.org, just file a ticket at http://dev.sugarlabs.org under the component localization, mentioning the name of the GIT repository. If your project is hosted somewhere else, please file a ticket detailing how to access your project's version control setup, and we'll try to figure out a way how to best integrate your project's translation related files.

			Basic steps for git.sugarlabs.org hosted projects:
			#) /po/ directory set up in top-level of git repo containing the .pot file produced by gettext.
			#) user:pootle granted commit priv to the repo
			#)Ticket opened in bugs.sugarlabs.org requesting hosting of project PO files in Pootle, please provide link to git repo.

	==== How do I start a translation team for my language ?====		==== How do I start a translation team for my language ?====

Dupuy: /* What do you mean by "string frozen"? */ lang-pap -> your language

2010-02-26T19:55:17Z

What do you mean by "string frozen"?: lang-pap -> your language

← Older revision		Revision as of 15:55, 26 February 2010
Line 73:		Line 73:
	:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.		:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.

	:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on ~~lang-pap~~ is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).		:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on your language is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).

	==== Is it possible to edit more than one string at a time? ====		==== Is it possible to edit more than one string at a time? ====

Dupuy: /* I have trouble translating the English to my language. Can I see translations in another language? */

2010-02-26T19:42:28Z

I have trouble translating the English to my language. Can I see translations in another language?

← Older revision		Revision as of 15:42, 26 February 2010
Line 90:		Line 90:
	:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.		:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.

	==== I ~~do not know~~ English ~~well enough to translate from it~~ to my language. Can I ~~get the original messages~~ in ~~any other~~ language ====		==== I have trouble translating the English to my language. Can I see translations in another language? ====
	: Pootle can show you the translations in an ~~intermediate~~ language while you translate. In order to see that, select the alternate language from your options page (once you have logged in)		: Pootle can show you the translations in an third language while you translate. In order to see that, select the alternate language from your options page (once you have logged in).

	==== How do I jump directly to the untranslated strings? ====		==== How do I jump directly to the untranslated strings? ====

Dupuy: /* What do you mean by "string frozen"? */ line break

2010-02-26T19:38:42Z

What do you mean by "string frozen"?: line break

← Older revision		Revision as of 15:38, 26 February 2010
Line 71:		Line 71:

	==== What do you mean by "string frozen"? ====		==== What do you mean by "string frozen"? ====
	:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to		:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.
	release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.

	:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on lang-pap is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).		:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on lang-pap is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).

Dupuy: /* General */ FAQ from cjl mailing list response, plus others from me

2010-02-26T19:38:02Z

General: FAQ from cjl mailing list response, plus others from me

← Older revision		Revision as of 15:38, 26 February 2010
Line 10:		Line 10:
	: See http://translate.sugarlabs.org.		: See http://translate.sugarlabs.org.

	==== I have a question that is not answered here - how do I contact you ? ====		==== I have a question that is not answered here - how do I contact you? ====
	: You can find on IRC at irc://irc.freenode.net#olpc-pootle. We also have a mailing list to ~~discussion~~ localisation related stuff. You can subscribe to the list by ~~visting~~ http://lists.laptop.org/listinfo/localization. You can also [[#ask a question]].		: You can find us on IRC at irc://irc.freenode.net#olpc-pootle. We also have a mailing list to discuss localisation related stuff. You can subscribe to the list by visiting http://lists.laptop.org/listinfo/localization. You can also [[#ask a question]].

	:If you face a problem that is affecting the way in which you (or others) would normally work, please mail [mailto:translate@rt.laptop.org translate@rt.laptop.org], stating the problems you are facing. The request will get logged in our Request Tracker installation.		:If you face a problem that is affecting the way in which you (or others) would normally work, please mail [mailto:translate@rt.laptop.org translate@rt.laptop.org], stating the problems you are facing. The request will get logged in our Request Tracker installation.

	You should use translate@rt.laptop.org for things like		:You should use translate@rt.laptop.org for things like
	* Forgotten passwords		:* Forgotten passwords
	* Error messages in Pootle		:* Error messages in Pootle
	* Pootle being unresponsive		:* Pootle being unresponsive

	:Requests like addition of new languages, addition of new projects, etc, follow the old workflow, and they should be done via Trac at dev.laptop.org.		:Requests like addition of new languages, addition of new projects, etc, follow the old workflow, and they should be done via Trac at dev.laptop.org.

			:The [http://www.translate.org.za Pootle developers] also have a mailing list for Pootle discussion - you can subscribe and or search the archives at http://lists.sourceforge.net/lists/listinfo/translate-pootle - however please post your questions to the SugarLabs/OLPC localization list above, as they may not be relevant to the larger Pootle community.

	==== Things that you should initially try to resolve your problems ====		==== Things that you should initially try to resolve your problems ====
Line 27:		Line 29:
	:* Avoiding searching or uploading for large files (e.g. Etoys). If you need to upload/merge a large file, mail translate@rt.laptop.org		:* Avoiding searching or uploading for large files (e.g. Etoys). If you need to upload/merge a large file, mail translate@rt.laptop.org

	==== Where do I find a list of language teams and their administrators ? ====		==== Where do I find a list of language teams and their administrators? ====
	: A current list of language teams, along with their administrators (if any) is available at [[olpc:Pootle#Sign-up]].		: A current list of language teams, along with their administrators (if any) is available at [[olpc:Pootle#Sign-up]].

	==== There are so many projects. Which one do I start off with ? ====		==== There are so many projects. Which one do I start off with? ====
	: It depends on the decision of the language team you are a part of. We recommend that you translate at least Glucose, Fructose (and Terminology, to ensure consistency) before moving on to the other projects.		: It depends on the decision of the language team you are a part of. We recommend that you translate at least Glucose, Fructose (and Terminology, to ensure consistency) before moving on to the other projects.

	==== I don't understand the nomenclature of the projects. Could you explain it to me ? ====		==== I don't understand the nomenclature of the projects. Could you explain it to me? ====
	: Here's a table for your reference:		: Here's a table for your reference:

Line 67:		Line 69:

	You can also refer to [[Translation_Team/Pootle_Projects \| this page]] for more details.		You can also refer to [[Translation_Team/Pootle_Projects \| this page]] for more details.

			==== What do you mean by "string frozen"? ====
			:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to
			release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.

			:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on lang-pap is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).

	==== Is it possible to edit more than one string at a time? ====		==== Is it possible to edit more than one string at a time? ====
Line 77:		Line 85:
	: Depends. Initially, Pootle's ability to import PO files is not enabled, and it will be up to each administrator (language/project) to decide if it will be allowed, who will have said ability and set up the appropriate workflow.		: Depends. Initially, Pootle's ability to import PO files is not enabled, and it will be up to each administrator (language/project) to decide if it will be allowed, who will have said ability and set up the appropriate workflow.

	==== How do I see/test/check my translations in action ? ====		==== How do I see/test/check my translations in action? ====
	: There are several methods to do that. See [[Translation_Team/Testing]] for the details.		: There are several methods to do that. See [[Translation_Team/Testing]] for the details.

			==== I am translating for a deployment of OLPC XO laptops. What version should I translate? ====
			:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.

	==== I do not know English well enough to translate from it to my language. Can I get the original messages in any other language ====		==== I do not know English well enough to translate from it to my language. Can I get the original messages in any other language ====
	: Pootle can show you the translations in an intermediate language while you translate. In order to see that, select the alternate language from your options page (once you have logged in)		: Pootle can show you the translations in an intermediate language while you translate. In order to see that, select the alternate language from your options page (once you have logged in)

	==== How do I jump directly to the untranslated strings ? ====		==== How do I jump directly to the untranslated strings? ====
	: From the project page of your language (eg: Fructose for Spanish), click on the ''Show Editing Function'', and for each file, you will get a link called ''View untranslated'' which would take you directly to the untranslated strings.		: From the project page of your language (eg: Fructose for Spanish), click on the ''Show Editing Function'', and for each file, you will get a link called ''View untranslated'' which would take you directly to the untranslated strings.

			==== How do I integrate translations into a software release/build? ====
			:A language administrator must perform the Commit to VCS action through the Pootle user interface, it is on the Translate tab of Pootle for those users like admins that have the commit PO file privilege. Pootle is directly connected up to the git software repository (git). The language admin's action in Pootle triggers a commit in the software repository; the PO file for that language can be found in the /po directory of the git project's source code tree and after the commit of the PO file, you can see the evidence in the git commit log and in the date stamp of the PO file in the source tree.

			==== Why are strings that were translated in Pootle not showing up in the releases/language packs? ====
			:Suggested strings will not appear in the committed PO file and will not be shown to users. Translations marked as "fuzzy" will be committed, but will not be built into activities or language packs; for these strings, as well as ones that have not been translated at all, users will see the English version. There are no functional consequences of partially completed PO files, but as you can imagine, it is not a pretty or desirable result to have mixed language UI strings.

			:For suggested strings to be incorporated in the translation, they must be accepted. Accepting or rejecting suggestions is done by language admins (or other localizers that may be granted the review privilege in a given language). It is generally part of the review process, which should take place before any commit, to clear up any pending suggestions.

			==== How can I translate Pootle itself into my language? ====
			: Especially when working with less technical translators, having Pootle operate in their native language can be helpful. While Pootle supports many languages, some of the language targets for Sugar do not yet have Pootle translations. Previously Pootle used the "live" translations from the Pootle project in the Sugar Labs Pootle server, but this is no longer the case. All translations of Pootle should now be done at http://pootle.locamotion.org/projects/pootle/ - if your language is not listed there, contact the Pootle developers on the translate-pootle mailing list and it can be added. Once the translation is substantially complete, contact us and the translated strings can be copied over to the Sugar Labs Pootle. In general, however, if your translation team is able to use Pootle in English or another supported language, it is better to concentrate on translating Fructose/Glucose/etc. first.

	=== Trouble-shooting ===		=== Trouble-shooting ===

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

2010-02-25T00:00:58Z

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

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

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

2010-02-24T23:53:08Z

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

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

Cjl: tweak

2010-02-09T02:34:55Z

tweak

← Older revision		Revision as of 22:34, 8 February 2010
Line 66:		Line 66:
	\|}		\|}

	You can also refer to [~~http:~~/~~/lists.laptop.org/pipermail/localization/2008-October/001732.html~~ this] ~~post in the localization mailing list~~ for details.		You can also refer to [[Translation_Team/Pootle_Projects \| this page]] for more details.

	==== Is it possible to edit more than one string at a time? ====		==== Is it possible to edit more than one string at a time? ====