Offline Word can be used to translate or correct jobs without having an Internet connection.
The offline word file is generated in the Offline Translation menu of a job and can be downloaded in the footer after generation. The editing of an offline word file must be done with the MS Office Word program. After editing, the file is uploaded again in the Offline Translation menu.
In the Offline Translation menu of a job, the view in the Word file can be configured
Structure of the Word file |
Description |
Application |
|---|---|---|
| Source and Target Language | The texts from the source language and the target language are displayed. | A normal translation job where it is important to compare the source and target languages. |
| Target Language Only | Only target language is displayed | Suitable for editing in target language |
| Source Language only | Only the source language texts are displayed. | There is only one input field per segment in the offline word file. The source text is overwritten by the translation. |
| Source, target and relay language | The texts from the source and target language as well as a relay language are displayed. | A translation job in which it is important to compare the source and target languages and at the same time to know how texts have been translated into another language. |
| Optional: Choice of a relay language | If source, target and relay languages have been selected, the desired relay language is selected. All target languages of the job are available. | Mandatory field if source, target and relay language was selected. |
| Optional: Insert TM suggestions | Translation suggestions from the translation memory are displayed below the texts. | Important, if translation suggestions from the translation memory are to be used. |
Result: The offline word file has been downloaded and can be opened and edited.
When editing, it is important to change content only within the designated fields. If fields are not to be imported into ONTRAM, the Translated drop-down can be set to the value Not Translated to the right of the segments.
Note: Copying and pasting from third-party systems, using change tracking, manipulating table structure, or changing content outside of the edit fields may cause problems in ONTRAM, or the file cannot be imported back.
Result: The job has been processed and can now be imported back into ONTRAM.
Result: The job has been imported. In addition, the system provides a summary of the import activities in an import log. This Protocol shall include:
Entry |
Description |
|
Start of the import |
Timestamp (server time) - start of the import process |
|
Duration of the import |
Duration of the import process in the format 0:00 |
|
Job language |
ONTRAM path of the job to which is currently being imported |
|
Imported file |
Imported file name |
|
Number of segments of the job |
Output number of all segments present in the job |
|
Number of imported segments |
Output, number of imported segments. The number of imported segments may be reduced due to errors (see Error section) or a segment status in the offline file. |
|
Error |
Output of faulty segments that could not be returned. This can be the case, for example, if placeholders have not been adopted into the target language or an incomplete inline formatting within a segment is detected. The system outputs the ONTRAM segment ID and an error description. Example: Error: Incorrect placeholders in segment 1_1-50-0-0. Missing placeholder in target language: {/style1} With the help of the ONTRAM segment ID and the error description, you can correct the error in the offline file and make a new import. Alternatively, you can try to return the corresponding text manually in the online editor. If this is not possible, please contact the ONTRAM support channel you have been notified. The ONTRAM team will assist you with the repatriation. |