Using OmegaT for guides translation

From The Document Foundation Wiki
Jump to navigation Jump to search
This page is a translated version of the page Documentation/Development/UsingOmegaT and the translation is 2% complete.
Other languages:
English • ‎español • ‎italiano • ‎português do Brasil • ‎русский • ‎한국어

OmegaT is an open source Computer Aided Translation tool. It is written in Java, translated into numerous languages and has a large community around it. We only describe here the necessary steps to use the tool with .odt files. Please read OmegaT documentation to know how to use it in your translation process.

Miloš Šrámek has made a presentation about his workflow (thanks a lot!), this wiki page describes the process based on the development he shared.

Using OmegaT

Download the software from the official site here: Even if you are on Linux, the packages offered via the distro repository are often outdated, so it is better to install the version from the site. Also, the Java version required may not be the one offered by your distro, so choose the version with the Java installer.

To install it, follow the usual way on Windows. On Linux, there is a script that will place the package in /opt and install Java at a user level in case of another system installation, so just run and you are done.

Now, download the guide you want to translate in .odt format. Launch OmegaT and follow these steps:

  • Create a new project named GuideTrans for example. This will create a new directory in your home directory
  • In the Project creation window, set the languages for the source and the target, let the segmentation checked
  • Select the location of the guide you downloaded in the File for source language
  • Let the other paths as they are, the corresponding directory will be created in the GuideTrans directory
  • Click OK, you are now ready to translate the guide

When you have finished your translation, create an .odt document that will be placed in the GuideTrans/target directory by selecting Create translated files under the Project menu.

Remember that under the project directory (GuideTrans in our case) you have several sub-directories that you can access: dictionary, glossary, source and target and translation memory. There is also several .tmx files (translation memory files) under the omegat directory. Again, do not hesitate to read the OmegaT documentation to go further with this helpful tool.

Adding UI.po file

The translation for the LibreOffice interface and help is maintained by the l10n teams via Pootle. The format of the files there are .po files. The .po files are spread across multiple directories, which makes working with them difficult. By using a tool called 'Translate toolkit' we can modify this structure to get a big .csv file. This .csv file can be added to OmegaT to serve as a glossary. The glossary has a major benefit: while translating, you will be proposed the exact terms used in the menus and the dialog boxes, which is very important for consistency and the quality of the guides.

So, how to get all this in place [those explanations are on Debian, if you know how to do it on Windows, please add them :)]:

  • First, download the UI.po file in your language from here: where XX is the code of your language.
  • Download and install the Translate Toolkit from here:, there is an installer for Windows. On Linux, if you already had an old version installed, it is recommended to remove it before installing a new one.
  • Create a directory (podir in our example) where you unzip the downloaded UI files
  • Then, use the command line to convert po files to csv files from podir to csvdir (where the csv files will be placed)
po2csv -i podir -o csvdir
  • We will now create the big csv file
cat `find csvdir -name \*.csv` > lo.csv
  • Now navigate to csvdir directory and open the lo.csv file with LibreOffice, remove the first column that contains comments and save the file as text csv using tab as column separators.
  • Copy the file to the GuideTrans/glossary directory.

Suggestions will appear on the Glossary area of the OmegaT window and on the contextual menu. You can also activate them using Options > Transtips > Unable Transtips.

Adding a 3rd file

The idea here is to add a third file that will serve as translation memory for the current translation. Imagine you have an old guide already translated that you want to update to the newest English version but based on the old one in your language. We will then transform an existing .odt old file in a .tmx file. Before the transformation, make sure that your file is clean of direct formatting to avoid extra tags to be created. Then:

  • Create a new project in OmegaT called Aux
  • Set the segment displaying so that it shows text only
  • Copy the old translated guide to the Aux/source directory
  • Now, using the mouse, copy all text for both files and paste it to a new file.
  • Save the new file as a txt file, check the alignment of the segment and correct it using this tool and then export it as .tmx file.

Manage a Team Project

This part explains how to use the Team Project functionality of OmegaT. The Team Project feature in OmegaT makes it possible for multiple translators to work on the same translation project, over the internet, using a synchronised project memory and a synchronised project glossary.

There are two parts in this guide. The first part will get you set up with the repository on GitHub to have the project synchronised. The second part is about how to set up the project on OmegaT. The team leader will set up the OmegaT part or ask Sophie on the Documentation project to set it for them, while the translators will only have to give the URL of the repository to OmegaT and translate as usual without taking care of anything else.

GitHub part

The first thing is to create a directory for your project on GitHub under the OmegaT repository. Well you need to be added to the OmegaT group too.

  1. To be added to the project
    • create an account on GitHub
    • ask Sophie to be added to the LO/OmegaT group
  2. Adding your language directory
  • you need to have svn installed on your computer
  • check out the repository using subversion to create a local repository:
svn co
  • enter OmegaT/trunk and create the xx directory where xx is your language code
mkdir xx
  • download and unzip This template has been prepared by Miloš and will create what is needed in your repository, which you can get from

  • change <target_lang>SK</target_lang> for <target_lang>XX</target_lang> in the LOGuides/omegat.project file, where XX is your language code
gedit LOGuides/omegat.project
  • copy the LOGuides and LOGuides-graphic into the OmegaT/trunk/xx directory
cp -r /source directory/LOGuides LOGuides-graphic OmegaT/trunk/xx
  • add your language (xx is your language code) repository to svn
svn add xx

(if you do not want the odg files with screenshots, either delete LOGuides-graphics or do not add it to svn. They may help, however, since besides screenshots there are also some drawings)

  • you may try to open the project in OmegaT now (do not do that prior to 'svn add', since OmegaT will create a few files, which should not be stored in the repository)
  • commit your language project (xx is your language code) with all the content inside
 svn commit -m "xx project added"

OmegaT part

  1. Open the project from OmegaT, replace xx by your language code in the URL:
    • use Project -> Download team project
    • enter "" in the Repository URL Box and hit tab - if OK, OmegaT will detect repository type and confirm that it is a subersion repository just below the field.
    • enter the name of the local work folder (or create it - do not use the original which you have used to check out by subversion)
    • Hit 'OK'. OmegaT in its lower left corner shows progress
  2. Start translating.

Any time you will save the project, it will be synchronized on GitHub, the glossary and the translation will be updated.

If there are other translators who want to work on the same project, they will need to create an account on GitHub. We will add them to the team and they will then have to follow the steps in the OmegaT part. They will never have to visit GitHub, everything will be handled by OmegaT.

The next steps are, as explained above:

  • create glossary with GUI translation using the .po files on Pootle
  • create tmx files from old translations to reuse them as a third file
  • have everything translated by "Google translate" to save a lot of typing

Testo pagina originale

Per familiarizzare con OmegaT si consiglia in primo luogo di fare riferimento alle guide presenti nella cartella condivisa su dropbox (al riguardo chiedere informazioni in lista di localizzazione).

In rete sono disponibili molte risorse; anche video su È anche possibile chiedere ulteriori riferimenti in lista di localizzazione.

Modalità di traduzione

Omegat offre diverse modalità di traduzione; è possibile creare un nuovo progetto sul proprio pc oppure lavorare a un progetto ospitato su server. Attualmente il gruppo di localizzazione di LibreOffice usa, per la traduzione delle guide, la modalità collaborativa online. Con questa modalità la guida da tradurre viene caricata su un server git, al quale ciascun localizzatore si collega nel momento in cui apre il programma Omegat sul proprio computer. Un documento aperto con Omegat viene automaticamente suddiviso in segmenti, quindi ogni volontario si occupa di tradurre un certo numero di segmenti, normalmente corrispondenti a un capitolo della guida. Per informazioni più dettagliate chiedere in lista di localizzazione.

Consigli per l'utilizzo

Di seguito alcuni consigli che possono tornare utili:

  • Avanzamento con il tasto Tab: nelle impostazioni scegliere “Avanza con il tasto Tab” (sotto menu Opzioni).
  • Tasti di scelta rapida più utilizzati (su Mac utilizzare ⌘ Command invece di ctrl):
    • ctrl+r → sostituisci con concordanza
    • ctrl+i → inserisci parte selezionata della concordanza
    • ctrl+f → cerca nel progetto
    • ctrl+t (ctrl+⇧ Maiusc+v per nuove versioni di omegat) → controlla tags
    • ctrl+s → salva
    • ctrl+d → crea documenti di arrivo (In caso di progetti ospitati su server github non utilizzare la creazione documenti in fase di traduzione; in fase di revisione utilizzare solo con progetto omegat scaricato in locale)
  • Per vedere a quale tipo di formattazione (nel testo originale) corrisponde un tag, posizionate il cursore sul tag e attendete un paio di secondi.
  • Dove necessario fare riferimento all'interfaccia di LibreOffice per verificare se la propria traduzione è corretta o meno (ad esempio per voci di menu e titoli di finestre, comandi , schede, etc); utilizzare la versione di LibreOffice corretta, relativa alla guida che si sta traducendo.
  • Rileggere il segmento dopo la traduzione.
  • Fare attenzione agli spazi; evitare di lasciare doppi spazi tra le parole (i tag ingannano!). Fare anche attenzione a lasciare gli spazi necessari tra il testo e i tag che corrispondono alle immagini delle icone presenti nel testo odt.
  • La consultazione dell'HelpOnLine può tornare utile.
  • Anche la ricerca nel progetto (ctrl+f) torna utile, per vedere come si è tradotta una certa frase nei segmenti precedenti, e mantenere così omogeneità nella traduzione. Le frasi identiche (tag inclusi) vengono comunque tradotte automaticamente.
  • Attenzione ai tag, che devono essere riportati sempre nello stesso ordine nella frase tradotta.
  • Un errore nei tag potrebbe causare problemi nell'apertura del documento tradotto, fino a renderla impossibile. Utilizzare il controllo tags per identificare potenziali problemi.
  • In caso di necessità è anche possibile cambiare la lingua dell'interfaccia di LibreOffice, per vedere come è stato tradotto un comando/finestra (Strumenti ▸ Opzioni ▸ Impostazioni della lingua ▸ Lingue).