Index

Objective

The objective of this guide is to demonstrate the operation of Fluig process translation system.

Generating Literal Files

In order to generate literal files for a new diagram, just check "Creates literal files" on the following screen:

When you check “Creates literal files”, three properties files are created, where literals are stored for the languages supported by Fluig - English, Portuguese, Spanish, as in the following image:

These files are created with three properties that are related to process information:

• process.category = process category;
• process.description = process description;
• process.instructions = process instructions.

The category, description and instructions fields can be regularly completed when modeling the process, without the need of any special translation technique.

However, this provided information is only used when importing, exporting and modeling processes. For opening and moving processes, literal file strings are used.

For older projects, the folder "literals" is created automatically, both when creating new diagrams and when importing processes with defined literals. For old projects and diagrams, the folder and the properties files can be created using the Eclipse "New Folder" and "New File" options, which also are available in Fluig mouse context menu.

The literal files created this way must follow the this convention:

(Diagram name) + “_en_US.properties” or “_es.properties” or “_pt_BR.properties”.

All three files must be created so that the process can be exported. All files should contain the three basic variables mentioned above as well as all the variables created elsewhere in the process.

For the content of literal files, we recommend the use of the Unicode system for replacing special characters, such as accented characters and the use of the cedilla and tilde.

The following is an example of the string "Aprovação de documentos fiscais" converted to Unicode:

process.description=Aprova\u00e7\u00e3o de documentos fiscais

The use of Unicode prevents code inconsistencies in process translation.

Translating Information from Activities, Objects and Flows

In order to translate information from activities, literals should be created using the following semantics:

(activity code) + "." + field to be translated = "desired string" .

Where:

Activity code: can be obtained by checking the properties of each element of the diagram, as in the following image:

Field to be translated: is what you want to translate. The field "name" represents the name and the field "instructions" represents its instructions.

In this line, when translating the activity with the code "task6", literal file will have the following activity:

• 6.name = "Financial approvement" .
• 6.instructions = "In this point of the process we have the financial approvement" .

For flows, besides the "name" property, two other properties can be used:

• Flow: string used as the value for the "Flow Activity" field;
• Return: string used as the value for the "Return Activity" field;