Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
74:export_for_translation [2019/08/30 14:48] – ndn74:export_for_translation [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Exporting a process for translation ====== ====== Exporting a process for translation ======
  
-Processes can be exported for translation by an external translator in Management > Process Versions+Enable "Use Multiple Languages" option via ''Administration>Workspaces'' (3-point-menue Edit > Properties) is precondition for exporting/importing processes for translation. 
 +=== Step by Step ===
  
-Click "Export for Translation" in the context menu of the process version that you want to export. +  - Click "Export for Translation" in the context menu of the process version that you want to export. 
- +  - A .zip file download will be created. This .zip file contains the process element names and descriptions in the default language of the current workspace. 
-A .zip file download will be created. This .zip file contains the process element names and descriptions in the default language of the current workspace.+  - The translator is expected to modify the contents of this .zip file and create an updated .zip file with the same format when translation is finished. This .zip file can be reimported into Stages.
  
 === Translation Exchange Format === === Translation Exchange Format ===
  
-The translation .zip file contains one folder for every translatable process element (including the process start page, tailoring and description elements). The folder names have the following format:+The translation .zip file contains one folder for every translatable process element (including the process start page, tailoring and description elements). 
 + 
 +{{  :74:translation_export_folders.png?nolink&579x171  |translation export folders (example)}} 
 + 
 +The folder names have the following format:
  
-  * For the process start page: process$//<process identity>// $ +  * For the process start page: process$//<process identity>//  $ 
-  * For top-level element folders: //<element type>// $//<element identity>// $Index +  * For top-level element folders: //<element type>//  $//<element identity>//  $Index 
-  * For process elements, including description and tailoring elements: //<element type>// $//<element identity>// $<element name> \\ Only the first 64 characters of the process element name are exported, and some characters that must not occur in folder names are replaced by "_"+  * For process elements, including description and tailoring elements: //<element type>//  $//<element identity>//  $<element name> \\ Only the first 64 characters of the process element name are exported, and some characters that must not occur in folder names are replaced by "_"
  
 The //<italic>//  parts in the folder names and the "$" characters must be preserved by the translation tool when the file is reexported. The //<italic>//  parts in the folder names and the "$" characters must be preserved by the translation tool when the file is reexported.