Translation System

This page will talk about the 2 task to run when doing a translation. It can be done by 2 different peoples :

• a translator that will just have to work in the OpenOffice spreadsheet, it's not technically complicated
• a manager that will set the files in SCENARIbuilder to get a new redistributable application from the spreadsheet and the original program sources. This requires some technical knowledge.

Translator

• Install the translation plugin
  • Download the last .jar here : http://scenari-platform.org/svn/dev-core/trunk/Bui_Utility/OOxliffFilter/out/
  • Launch OpenOffice, go to Tools > XMLfilterSettings > OpenPackage, and open the .jar you downloaded
• Translate the files
  • You will receive 1 or 2 ODS files by email
  • Open them with OpenOffice
  • Translate the "Target" column
  • The document may be protected. Go to Tools > Protect the document, and uncheck the boxes
  • If you have a dictionary and want to use the automatic correction, then right-click on the right column (the one that has to be translated) > format the cells... > Font and change the language.
  • Send them back by email

Conseil

Dont touch the Source column, don't add or remove columns, don't touch to anything except the Target column content You should not make a "word by word translation", the best would be to know the program you translate well enough so you get an idea where the text will appear on the program, and know in what context they were used. The aim is to make a translation that will not confuse the user (making harder to understand how the program works or more human-error prone). You will find that many words are related to Scenari and doesn't really have just one perfect translation above all other in your language. Try to identify them, and use the same words if appropriate, to make a coherent Scenari vocabulary. Preserve whitespace, special sequences when they are not part of any language rules. For example if the text is " Prévisualiser...", translate it to " Preview...". Some special sequences might be like a phrase with "Voulez vous vraiment supprimer l'item %1$ ?". In this case, "%1$" would be a special sequence that will be automatically replaced by the filename while the program is running if the message appear, so you need to preserve it in the translation. Like "Are you sure you want to delete the item %1$?" Apply typeset rules of the language you are writing for. For example, in french, you write a space before ":", but in english, you do not need that. Save often (as an ODS document) If you don't really speak french you can translate it from english, assuming the french -> english translation already exists.

Manager

Translating the main parts of opale

Translating the main parts of the opale editor and generators, then creating the wsppack files using this translation is reasonably simple. Most of the Opale vocabulary and the generated documents will benefit from the translation, but the scenari menus and the common parts in "SCENARIchain" will still stay in the default language. (to be completed)

full translation

Translating everything in the application (including the "core" files of Scenari), then creating new installers is a more technical task. (to be completed...)