Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TypeNameUsageMandatory
DirectoryproofReadContains a files and/or a folder tree with the files, that should be imported into the segment table of translate5. The folder tree inside of proofRead will be mirrored as folder tree inside of translate5.yes
DirectoryrelaisContains a structure that mirrors the structure in proofRead. This means, all directory and filenames must be identical with the names in the proofRead directory. All contained files are imported as relais/pivot content for the files in proofRead. Files existing in "proofRead" but missing in "relais" are skipped.no
DirectoryreferenceFilesReference files that are attached to a task for download. Additional information for the user working on the task.no
File*.tbxContains the terminology for the task. The contained terminology is used to mark terms in the task. Must reside on the top level of the zip-file. Only the first tbx-file in the zip file is used. Please see here for information, which terms are used for a task.no
FileQM_Subsegment_Issues.xmlContains the MQM issue types, that should be used for the task. If present, overrides the default MQM issue types for this task. An example file you find here.no
Filetask-template.xmlContains a task template. Can be used to configure translate5 in an task-specific way.no
FileDEU-ENG.transitConfig

Only for import packages, that contain STAR Transit NXT files.
The first three letters of the file name must contain the transit-specific source-language file extension (in the example "DEU" for German).
The last three letters of the file name (before the file extension ".transitConfig") must contain the transit-specific target-language file extension (in the example "ENG" for English).

The file itself can be empty. It is a flag file.

no
File*.bconfThis is a batch configuration file as exported from Okapi Rainbow. With Okapi Rainbow you can create your own custom file filters, for example for special kind of xml or txt-files. If you use the Okapi plugin for translate5, you can seemlessly use Okapi in the background to convert files on import time - and convert them back on export (without the user having to touch Okapi). Please see details on the translate5 file format page and on the translate5 Okapi Plug-in page

...