Interoperable interactive geometry for Europe
I forgot my login data

Report a bug

Fan club

Quick Intro Videos
click to start movie
Create A Simple
GeoGebra Resource (25Mb)
click to start movie
Filing a review
click to start movie
Find a Resource

This platform is brought to you by the intergeo project, funded under the eContent Plus programme of the European commission and by partners

Intergeo Translator's Manual

2geo Translators Manual

The Intergeo Consortium

September 2008

Version: submitted version of Aug 07, 2009

Main Authors:

Santiago Egido (Maths For More, S.L.)

1  Introduction

Thank you very much for volunteering to translate 2geo, the European leading site on Interactive Geometry associated to the Intergeo project. This page has already been translated to English, French, German, Hindi and Spanish, and other languages are in the process.

2geo is built upon Curriki, which is itself built upon XWiki, and therefore you may find that you have already used before its translation tools.

2  Becoming a translator

In order to become a member of the Translator's group you will have to:

  1. Get an account on 2geo. Visit, click on the "Become a Member" button, and follow the instructions.
  2. E-mail the translations coordinator ( and tell him your user name, so that he can give you access to the files.
  3. Join the translators group. Visit, click on the "Join this group" button at the end of the page, and follow the instructions. You should check occasionally this group, to see whether there are new messages that apply to you.
  4. Before you start translating, you should read the 2geo's Basic User Manual (available at, and browse some other documentation on the site, so as to get an idea of what 2geo is about.

3  Page translation and translation files in 2geo

Most of the text you see in 2geo is contained in translation files. Some texts are not really part of the pages, but strings entered by users, and so have no translation; for instance, the name of resources is provided by their creators, and everybody sees them in the language they were written. There are also a few pages whose text does not come from the translation files, but we can ignore them.

Each translation file is just a list of "properties".

Lines starting with a "#" are comments and need not be modified (although it's a good idea to read them anyway, since they might be useful hints). You could add your own comments to write down alternative translations or document changes.

The other lines have this format:

property name=English string

You should translate only the strings in English, leaving untouched the property names.

When a page is constructed in your language, your files are used to search for the strings through the property names. Sometimes it is obvious in which pages these strings are used, and how, so that they are easy to translate. However, some strings are error messages that you will not see normally, and others properties are very short and ambiguous phrases used to construct longer sentences, such as "yes", "none" or "the", which might be translated in several ways. In order to decide among several possible translations, look for hints at the name of the property and at nearby comments and strings. For instance, in the middle of a set of strings referring to mails, it is pretty safe to assume that a "not found" string would refer to "mails" and so it should be translated as plural and with the same gender you have used before for "mails".

Some strings contain argument locators where something is to be replaced. For instance, in "The password for {0} has been emailed.", the {0} will be replaced for the username. You are to translate the whole sentence, feeling free to move the argument locators as you see fit. For example, a string such as "{0} is not in {1}" might be better translated to your language as "{1} doesn't contain {0}".

When you find an encoded link such as "members list ?", translate only the first part, before >, "members list". If you find a link such as "Group Name?", do not translate it.

4  Getting access to the translation files

There are three ways to work on the translation files:

  • by being a member of the Translator's group;
  • by being an administrator;
  • by getting the files by e-mail.

The recommended method is becoming a member of the Translator's group; you can then go to and edit the files as described in the next section.

Administrators can also visit that page and edit the files, and also translate pages. However, administrators can make big mistakes, and so this option is reserved to website developers.

Working on files sent by mail is very easy, but you won't see immediately the effects of your changes on the website, and so it is not the best option. The accents and special characters should be encoded in UTF-8, and it doesn't matter whether the line ends are Unix's or Windows'. If you have not understood this, then don't worry, the translations coordinator will fix it.

5  Editing The Files online

(As an alternative to reading this section, you might want to see the video at

Go to Select your language in the combo-box.

For each translation file there are two links; the first one is just to view it, and the second is to edit it. The viewing page looks like this:

If you saw the pencil icon to the left, you could click on it to edit the file without having to go back to the previous page. If you were an administrator, you could click on "Edit" button at the left, upper corner to edit this file. Most likely, the only way available to you to edit a file will be to click on the edit link in the translatable files pages. Any one of these three actions will lead you to the edition page, which looks like this:

You can ignore the "Title" textbox; it is useful in editing other kinds of content. When saving your work, you are asked for a short description of the changes you have done (if you haven't entered it already in the "Comment" textbox); you can leave this description blank, but this information might be very useful in tracking errors.

You are strongly encouraged not to use the "WYSIWYG" and "Access Rights" buttons.

While you are translating online, you can:

  • Click the "Cancel" button to quit without saving your changes.
  • Click the "Save and Continue" button to save the changes you have done so far and keep on translating; if you Cancel after this, the only changes that will remain will be the ones done before clicking "Save & Continue".
  • Click the "Save & View" to save your changes, stop translating, and view the file as it is right now.
  • Click the "Preview" button to see the file as it would be saved if you chose to save your changes. In the viewing page you cannot edit; if you want to keep editing, click on "Back to Edit". You are also given the options to "Cancel", "Save & Continue", and "Save & View", which do the same as the edition page buttons.
  • You are strongly discouraged from using the text format buttons and specially the WYSIWIG editor, which may corrupt the translated file.


When you save data, make sure the file you are saving is in your language.

When you start working, your file will be just a copy of the English file. If you erase some original content, you could open a new window and use it to view the English file. However, it is a dangerous idea to edit the English file to view it in the same size as your file: it is very easy to get confused and make changes in both files. Edit your file, and only view the English file.

You can see at any time any page in any language; there are two ways to do this:

  • "The 2geo way": visit the page and select the desired language in the language selector box in the header (this will fail in pages without header).
  • "The Curriki way": visit the page and add at the end of the URL a string like "/?language=fr" if you want to see it French, "en" for English, etc.

6  Translating Pages

It is not expected for 2geo translators to have to translate pages. This section is a "just in case" piece of information; you may skip it, or watch instead the video at

Most pages in XWiki can be translated just by editing their content, although the procedure described above is preferred (just to mention two advantages of property files over translating pages, the texts defined through properties can be used in different pages, and you can translate error messages without having to produce them).

In order to translate a page, you need to have edition rights on it. If you are an administrator, then you can edit anything.

You have to:

  1. Log in as an administrator (or as someone with edition rights on the page).
  2. Go to the page you want to translate.
  3. Click on the "Edit" button at the top left corner of the browser. In the yellow block to the right you can see which document you are editing:

    If this page has never been translated before to your language, you will have to create a copy of it in your language; in order to do this, just click on your language link, and you will be editing the version of the file in your language:

  4. Translate as indicated in the previous section for navigation elements. Depending on exactly which page you are editing, you may see HTML code or Wiki syntax; translate only the visible text, and leave untouched the tags. You can find help about the Wiki syntax at If you damage your file, you can compare with the original in English. Make sure you don't save changes while editing the original file!
  5. As before, when you save your work, make sure you are editing your language.

7  Translations coordinator manual

7.1  Adding a new language

In order to add a new language to the list of languages supported by 2geo, the following tasks have to be performed:

  1. Go to, add the new language to the list, and save. Wait one night for the change to take effect.
  2. Add the new language the in the Global Class Translations bundle, at least in English (the other languages will have to have its translations updated).
  3. In order to add the new language to the skills-text-box, add the new language in SkillsTextBox.gwt.xml as supported language, and then send a mail to the wp4 mail list so that skills-text-box is recompiled.
  4. In order to add the new language to the Currikulum Builder, edit XWiki.AssetClass with

7.2  Adding someone to the Translator's groups

IMPORTANT: there are two translators groups!

  1. One is an XWiki group; that is, an administrative tool which grants access to XWiki resources (the translation files in this case). Typical users are not aware that these groups exist, and so you should subscribe new translators into this group without bothering them with the details.

    Go to the Administration page, in the "User Administration" block click on "Groups", then in "Translators Group". In order to modify the list, click on the "Edit" button on the top, left corner.

  2. The other is the Translator's Group, a Curriki group where the translators can send and receive e-mail messages, etc. Translators can join in two ways:

7.3  Managing bundles

This is done in

7.4  Curriki's Compare Tool

There is a tool, available only to administrators, which will find out which file entries have not been translated. This may be useful in detecting errors. In the Administration page, search for the "Compare tool" next to the files to be translated, and click on it. Select the file, "English" on the left, and your language on the right, and click on "Compare".

7.5  Translation Update Tool

When new properties are added, translations have to be updated. This may be due to the addition of a new feature to 2geo, a Curriki upgrade, etc. Updating a translation is a small operation compared with the task of translating all of 2geo, and there is a tool designed to do this as quickly as possible; just notify translators that a translation update is needed, and send them to, where they will find a list of the changes they have to do.

For an older version of this tool, a Java class that had to be run locally and then the new language files had to be uploaded manually to 2geo, see
TranslationUpdateToolDescription. Most likely this tool won't be needed, and, if needed, the only person which should use it is the translations coordinator (remember that translators may not know how to run Java classes).

File translated from TEX by TTH, version 3.85.
On 07 Aug 2009, 18:41.