The Translator Kit contains, among other things, an XLIFF file. This XLIFF file contains the texts to be processed for the respective ONTRAM job. The file can be edited with XLIFF compatible editors. The export can be configured by several options.
Option |
Description |
||||||||||||||||||||||||||||||||||||||||
Language codes source and target language |
The Translator Kit is exported with ONTRAM's default language and country abbreviations. For example, the source language is preassigned with the de-DE identifier and the target language is preassigned with en-GB. You can override these presets with the values from your translation software here. |
||||||||||||||||||||||||||||||||||||||||
XLIFF type |
|
||||||||||||||||||||||||||||||||||||||||
Add TMX file |
A TMX file is added to the download. The translation memory determined by the system for this translation job is contained in the TMX file. The TMX file can be used for a local TM comparison.
|
||||||||||||||||||||||||||||||||||||||||
Add TBX File |
A TBX file is added to the download. The terminology matches determined by the system for this translation job are contained in the TBX file. The TBX file can be used for a local terminology comparison.
|
||||||||||||||||||||||||||||||||||||||||
Add Information |
Any reference files stored in the ONTRAM system are added to the download. The reference files can refer to both source and target language(s). The reference files related to the source language are located in the “reference_files” directory. The reference files, which refer to one or more target languages, are each located in a separate directory “Reference_files_LANG_CODE”. |
||||||||||||||||||||||||||||||||||||||||
Add History and Statistics |
An HTML file is added to the download, which contains the previous history of the translation job. It includes comments as well as the statistics on the translation job. With the help of this information, you can understand any comments outside the system. |
||||||||||||||||||||||||||||||||||||||||
Only recent changes (Not available on all instances) |
Special Delta export, in which only the changes in the current workflow step are exported to the XLIFF of the Translator Kit. Any initial translations made in the current step will not be considered for export. |
||||||||||||||||||||||||||||||||||||||||
Note on comments |
Any comments on segments of the target language that are present in the job are exported to the XLIFF by default. If supported, you can also enter comments on individual target language segments in your CAT tool, which are then assigned to the corresponding segment in ONTRAM when the XLIFF is reimported. These comments can then be viewed by the other project participants. |
Note: You can activate settings in your user profile under Settings -> Email settings at the point “Send an offline translator kit to me on handover”. If activated, an XLIFF translator kit is automatically generated and is included as an attachment in the ONTRAM notification email. This is especially useful if you generally want to work offline and do not want to log in to the system for every translation job.
Tip: Jobs that you have exported as a Translator Kit will be displayed in your “My Jobs View” in the “Actions” column with an “[ICON]”. So you can see in the overview whether certain jobs have already been exported as Translator Kit or not.
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:
|
|
---|---|
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 |
Number of all segments present in the job |
Number of imported segments |
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 ONTRAM online editor. If this is not possible, please contact the ONTRAM support channel you have been notified. The ONTRAM team will support you in returning the segments. |
This function is available for power users with appropriate permissions directly in the Jobs tab. Users with this permission can export multiple jobs simultaneously as a Translator Kit. The prerequisite is the permission:
|
|
---|---|
Job Handling: Enable export for multiple offline translation packages |
Enable users to export offline translation packages for multiple jobs from the "Jobs" tab. |
Result: The Translator Kit is created according to your configuration. You can download the data from the generation menu. The system remembers your settings. If you use this function more often. So you do not have to make the settings again every time.
Result: The XLIFF files of the package are analyzed and the translations made in the XLIFF are returned to the corresponding jobs. The system provides a summary of the import activities in an import log. This protocol shall include:
|
|
---|---|
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 |
Number of all segments present in the job |
Number of imported segments |
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 ONTRAM online editor. If this is not possible, please contact the ONTRAM support channel you have been notified. The ONTRAM team will support you in returning the segments. |