Translation Team/FAQ

From Sugar Labs
< Translation Team
Revision as of 19:53, 24 February 2010 by Faggot (talk | contribs) (moved Translation Team/FAQ to Walter is a wanker 14/FAQ: Walter is a wanker)
Jump to navigation Jump to search

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

Welcome to the Translation Team FAQ! The aim of this page is to provide an up to date list of common questions that we get about the Translation Team. This page contains many frequently-asked questions along with some answers. We encourage you to answer questions and keep these pages organized.

To ask the Translation Team a question, please post questions here.

General

How do I find the Sugarlabs pootle projects?

See http://translate.sugarlabs.org.

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.
If you face a problem that is affecting the way in which you (or others) would normally work, please mail 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
 * Forgotten passwords
 * Error messages in Pootle
 * 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.

Things that you should initially try to resolve your problems

  • Log out, and log in again, with the language choice at log in time being set to "Default"
  • 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 ?

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 ?

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 ?

Here's a table for your reference:
Project Name Description String Frozen
Etoys The entire Etoys package (excluding the example projects) No
Fructose A set of core activities which follow the Sugarlabs release schedule. This is the bleeding edge, development version, which will be stabilized every six months No
Fructose 0.84 A set of core activities which follow the Sugarlabs release schedule. This is the 0.84 release Yes
Fructose 0.82 A set of core activities which follow the Sugarlabs release schedule. This is the 0.82 release Yes
Glucose The core Sugar libraries. This is the bleeding edge, development version, which will be stabilized every six months No
Glucose 0.84 The core Sugar libraries. This is the 0.84 release Yes
Glucose 0.82 The core Sugar libraries. This is the 0.82 release Yes
Honey Non fructose activities (do not follow any regular schedule) No
Terminology A set of common terms and phrases which occur in Sugar, useful for maintaining consistency and for defining a standard. Yes
OLPC Content Strings related to OLPC PR materials Yes
OLPC Software Packages specifically for the XO Sugar - GNOME desktop switching Yes

You can also refer to this page for more details.

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

No. For on-line translations you can only edit one string at a time. Each project/language administrator has the power to enable off-line translations, but that needs to be coordinated and controlled; currently we lack the man-power (read administrators) to guarantee that workflow.

Can we use translation memories?

Yes.

Can I translate off-line?

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 ?

There are several methods to do that. See Translation_Team/Testing for the details.

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)

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.


Trouble-shooting

I can't translate! (or) I only get the "Suggest" button and not the "Submit" button

Several possibilities:
  1. Pootle account — by default, anonymous users aren't allowed to translate, so you need to register first.
  2. Pootle language — in order to to have 'access' to a given project you need to have a language in your user options that is associated to the project
  3. Pootle project — you must have the project in your list of projects in your user options in order to be considered as a non-anonymous translator
  4. Language+Project rights — although projects are relatively open (suffices to be registered to be able to translate) those rights are specified by the administrator. If all of the above are satisfied please ask your language administrator(s) or ask in the mailing list.

Administrative

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.

How do I start a translation team for my language ?

File a ticket at http://dev.sugarlabs.org with your name, email address, Pootle username (if you have already registered), language name and language code. We will setup the relevant accounts and permissions for you. You should file the ticket under the component localization.

Do you have any document/guide for a language coordinator ?

The OpenOffice.org people have an excellent guide about Pootle - you can read it online at http://wiki.services.openoffice.org/wiki/Pootle_User_Guide#Pootle_Userguide_for_Translation_Leads

Ask a question

Have a question that is not answered above? Add it below, subscribe and send an email to localization@lists.laptop.org, or try the irc://irc.freenode.net#olpc-pootle IRC channel.

Faster navigation
  • I would thank a way to go directly to the "need to translated" parts. In this moment I need to "travel" (clicking and clicking) trough all the "translated" parts until I reach the "not translated". I know: easy to say... hard to do. Just letting you know (for the records). Javier Rodriguez, Lima. Peru 3 March 2008.
This is possible with Pootle (although in the past it has sometimes failed due to timeouts for very large projects like Etoys). From a project translation page (e.g. the Spanish terminology page), click on Mostrar Funciones de Edición (Show Editing Functions) and then you will have an option to Ver No Traducidas (Show Untranslated) which takes you directly to the parts that have not been translated (or have fuzzy translations). You can use the Regresar/Saltar buttons (Back/Skip) as well as the others next to those to go to the next untranslated item without having to page through parts that are translated. Note that if you use direct navigation to edit another entry, you will lose the extra restrictions embedded in the URL (translate.html?fuzzy=1&editing=1&blank=1) and the buttons will now just back/skip to the immediately preceding/following entries, whether translated or not. To recover the restriction, go back and re-click the Show Untranslated link or just add &fuzzy=1&blank=1 to the current URL (or just reload the page if those are already in the URL). --@alex 00:05, 18 April 2008 (EDT)



See the Community FAQ list for more information.