Alfresco Translation Guide

Swedish Language Pack TMX

This short guide is for those of you who wish to do your own translation of Alfresco, or participate
in the ongoing effort to keep the Swedish language pack up to date. There is also a section included
for other translation projects on how to set up and convert to use tmx for translations.

This guide is work in progress, please report any typos or improvements you may find.

Author
Peter Löfgren, Redpill AB

Tools Needed
You need to download OmegaT from http://downloads.sourceforge.net/omegat/
Choose the 1.8.0 update 2 version or any later version if you want spellchecking.

OmegaT is a Translation memory application written in Java, and it is free, license is GPL.
Read more on http://www.omegat.org/
NOTE: This guide is not intended to be a complete guide to OmegaT, please use the OmegaT help
to learn all the features available.

Checkout project
Use subversion to check out the project.
svn checkout https://forge.alfresco.com/svn/swedish

When you project is check out you will have the following project structure.
Alfresco_sv_SE Top folder
glossary Glossary files that shows up in the glossary pane to aid
you on how to translate specific words
omegat The main omegat tmx file with all the translations.
OmegaT creates backups when saving so you will see
lots of bak files. These can just be ignored.
source This is the directory for files to translate. They are
directly referenced from the Alfresco subversion library
target This is where your translated files go. It will initially be
empty.
tm Put external translation memory files here. Se separate
topic.
You should not need to edit any files manually in these folders, the only exception being glossary
files of you need to update/add glossary terms.
Running OmegaT
Before you start using OmegaT change the font to a font that make it easier to spot if it
is '' or “. Use Courier New or any other font of your preference.

Navigate to your checkout folder. OmegaT will recoginise this folder and display with a special
icon. Select and click open.
You will be presented with a list of project files. This gives you an overview, but you will also be
able to move directly to any file you wish to work with by following the link.

Translating segments
Each set of value pairs in the properties file is called a segment and needs translation. Just start
typing away, hit enter and move to the next segment to translate.
And there are features at hand for you, have a look at OmegaT help.

Update properties files

Before starting OmegaT, run svn update in your checkout directory.
Start OmegaT, it will now pick up any new files, or untranslated segments in existing files. Just
press ctrl+U and the next untranslated segment is presented to you. There is no need to do use any
comparison tools, OmegaT will pick up what has changed.

Generating the translations

Chose 'Project' and then 'Generate Translated Documents'.
Your translated files will be place in the folder target with subdirectories reflecting the diroectories
in the source directory. Deploy your translated files to a TEST environment and verify that they
work.
TODO: Add packaging instructions.

Spell checking
OmegaT allows you to use spell checking. You need to have OpenOffice installed (or download
dictionaries separately). In Options, select Spell Checking and navigate to your dictionary folder.
OmegaT will select the correct dictionary based on language in your project.
NOTE: I have not been able to get the 'Add to dictionary' feature to work, it forgets between
session. Still it is a valuable tool to spot typos.

Glossary
The directory glossary is where you put your glossary files. They are just text files with a term on
each row; source language TAB translation TAB explanation.
If OmegaT finds a matching source word it will show this in the glossary pane, along with
suggested translation and explanation.
Use the glossary to get a consistent translation and a reminder on how you translated the last time.
Note, for any new terms added, OmegaT has to be restarted to pick them up.

External TMX
You may wish to add external Translation Memory files that can assist you in your translation.Once
downloaded, drop them in the tm folder for your project. Do NOT add them as permanent part of
the Swedish translation project, it is for each translator choice and use.
You can download from here. Make sure you abide any licenses that applies.
http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx24/
This is OpenOffice translation memories. They have been tested for the Swedish translation, it will
rarely match completely but will give you an indication of how they have translated particular
words in OpenOffice.
http://langtech.jrc.it/DGT-TM.html
European Commission translation memory from the Join Research Centre. Not tested, and requires
some work to extract the languages you want to work with. Probably more legal/political translation
than software...
TODO: Add more if someone can find any publicly available.
Setting up a new project.
These instructions is intended for those who wish to set up their own translation project from
scratch, for example other translation project that wish to use this model.

Create a new translation project from the Project menu, select new

Select your source language, in the Alfresco case this is EN-US. Then set translated language.

Use the proposed default settings. You may if you wish override these setting, be sure you
understand what each directory do.
Convert existing translation to TMX
There is a tool Java .properties Import on OmegaT sourceforge that will convert your existing
translations to a tmx file.
Once you have a tmx file, put it in the tm folder and start your project. If there is a match it will
show up in the Fuzzy matches pane. You can configure OmegaT to insert you translations
automatically, but you will have to step through the entire project once. When done you can remove
your imported tmx file, your translated tmx file will from now on reside in the omegat folder.

Subversion configuration.
To add externals, mark your source directory, choose properties, subversion tab.

Add the property externals. This is what is used for Swedish Translation project
repository svn://svn.alfresco.com/alfresco/HEAD/root/projects/repository/config/alfresco/messages
web-client svn://svn.alfresco.com/alfresco/HEAD/root/projects/web-client/config/alfresco/messages
mediawiki svn://svn.alfresco.com/alfresco/HEAD/root/modules/mediawiki-
integration/config/alfresco/messages
webscript-framework svn://svn.alfresco.com/alfresco/HEAD/root/projects/webscript-
framework/config/alfresco/messages
extranet svn://svn.alfresco.com/alfresco/HEAD/root/projects/extranet/config/alfresco/messages
slingshot svn://svn.alfresco.com/alfresco/HEAD/root/projects/slingshot/config/alfresco/messages
Note that the name before the svn url can be named as you like. Any forge project using subversion
you would like to include and that has put the messages files in a separate directory can be added as
well.
To avoid adding backup files, subversion ignore some files.
● OmegaT creates a lot of backups of your translations, so in the omegat project folder, put
ignore on *.bak.
● Also put ignore on the project root folder for *.tmx, these are just files created in other tmx
formats if you wish to use another translation memory tool.
● In the target folder, you may choose to ignore each of the target subfolder names. They do
not need to be versioned. Unless you would like them to be for users to download translation
directly form repository.