Translations > Software > Functions > Process translation 

This function is used to:

  • view the processes to be translated. The LANTRA and LANREF parameters make it possible to pre-enter the translation language and the reference language.
  • extract the texts entered in the processes in order to perform the translation with softwares supporting the translation of XML files. The extraction is performed in a default xml directory created, if it does not exist, in the documentation directory defined by the DIRDOC setup.

Screen management

Translating a process

Two methods can be used to translate processes. The first two points are common to both methods.

1. Enter the destination language of the translation and the original language ("Translation reference" field).
Leave the boxes "All modules", "All codes" and "All legislations" checked in order to search all processes to be translated; or else uncheck these boxes, tabulate and perform a selection to filter your search.

2. Click on the button [Search] in order to launch the search of processes for which the translation is not up to date.

Translating using export and import functions

3. In the table, double-click in the "To process" field and select the value "Yes". Tabulate.

4. In order to extract a process in xml format, click on the [Export] button.

5. After translating files using an external software, re-import the translated xml file using the [Import] button.

SEEWARNING  The export of several processes generates a single file PROC_XXX. The import recovers the number of files (one file per translated process).

Translating using the "Detail" window

3. Perform a right-click on the line and select the "Detail" function.

4. Click on a table line in order to select a text. The corresponding code is displayed in the "Text" field.

5. Click on the button "Initialize text to be translated" in order to display the exact same text in the second text field. You can enter your translation directly in this field, making sure the existing syntax is respected.

6. Save the translation using the [Update translated text] button.

Tab Entry creation screen

Presentation

The header is used to specify the target language of the translation and the reference language.

Close

 

Fields

The following fields are present on this tab :

Block number 1

Defines the translation language.

Defines the language from which the validation of the translation is verified.

In the case of the extraction of an XML file for translation, the extracted text will be that in the given reference language.

Selections

  • All modules (field ALLMOD)

Used to indicate one module or all as a search criterion.

  • To translate (field ATRAD)

Uncheck this box to display the list of all existing, to be translated or already translated processes.

  • All codes (field ALLCOD)

Used to indicate the search criterion for a code range by using the start and end range or all codes.

  • All legislations (field TOUTLEG)

Leave the box "All legislations" checked in order to search the processes with a blank legislation or a legislation corresponding to the connection language of the folder.
Uncheck the box "All legislations" and tabulate in order to specify a legislation or to search the processes linked to a specific legislation.

Grid Search

  • To process (field PROFLG)

Used to define if the line must be processed when the process is launched by the button at the bottom of the screen.

Starts the process for the current line of the table. This produces the XML file that will be used to perform the translation.
Indicate a directory were the XML files will be extracted. This directory corresponds by default to the xml sub-directory of the directory selected to store the documentation extracted in HTML format.

  • field VLDDATREF

Indicate the validation date or the last modification found in the object for the selected reference language.

  • field VLDDAT

Indicate the validation date or the last modification found in the object for the selected translation language.

  • Existing (field EXIST)

The checkbox indicates that at least one text of the process is translated for the chosen translation language.

  • Incomplete (field INCOMP)

The checked box indicates that some texts are not translated.

Close

 

Action icon

Standard rerouting action

When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer Yes to all the lines starting from the current line.

Standard rerouting action

When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer No to all the lines starting from the current line.

Detail

Fields

The following fields are included in this window :

Block number 1

 

Defines the translation language.

Defines the language from which the validation of the translation is verified.

In the case of the extraction of an XML file for translation, the extracted text will be that in the given reference language.

Grid

  • Reference (field IDTEXT)

Indicates the number associated with the text to be translated.

  • field VLDDATREF

Indicate the validation date or the last modification found in the object for the selected reference language.

  • field VLDDAT

Indicate the validation date or the last modification found in the object for the selected translation language.

  • Updated (field AJOUR)

If the box is checked, the translation of the text is updated. It does not require a translation.

Block number 3

  • field CLB1

Code of the original text.

Block number 4

  • Reference (field IDT1)

Indicates the number associated with the text to be translated.

  • Initialize text to be translated (field INIT1)

This button is used to display or update the text to be translated in the destination language (if the text has been modified since the last translation).

Block number 5

  • field CLB2

Code of the text in the destination language. This field is empty when the text has never been translated.
Click on the button [Initialize text to be translated] so as to display/update the text of this field. The translation can be performed directly in this field or by changing the text in the original language or the text of the old translation (if the text was recently modified).

SEEINFO Be sure to respect the existing syntax and not to delete tags.

Preview

  • field VISUT

Displays the selected text.

Block number 7

  • Update translated text (field MAJ)

Click on this button to save and update the text after translating it in the "Text" field.

  • Display of reference text (field VISUREF)

Click on this button to:

  • display the text in the original language in the "Preview" field,
  • interpret html tags so as to display the code in "Wysiwyg" mode.
  • Display of translated text (field VISUTRAD)

Click on this button to:

  • display the translated text in the "Preview" field,
  • interpret html tags so as to display the code in "Wysiwyg" mode.

Close

The [Detail] button opens a window used to manually enter the translation of processes.
A table displays all the texts of the selected process. These texts are sorted by number and their content, in the reference language, can be accessed in the "Preview" field by right-clicking on the corresponding line.

Preview

The "Preview" function is used to display a non-modifiable image of the process.

 

Close

 

Specific Buttons

The process translation function makes it possible to search processes that do not have an up to date translation, using the [Search] button.
The search can be limited to a specific module, code, legislation or code range. It is then possible to manage processes for a unit or a group by right-clicking on a line.

This button is used to extract a file in the xml format on the workstation of the customer. Choose the destination directory and click on the [Select] button.

This button makes it possible to import an xml file in Sage X3. Choose the source directory of the file and click on the [Select] button.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation