|Type||Name||Usage||Only available with listed plugin||Mandatory|
|Directory||proofRead||Contains 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|
|Directory||relais||Contains 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|
|Directory||referenceFiles||Reference files that are attached to a task for download. Additional information for the user working on the task.||no|
The contained files are used to generate a layout for visual translation or visual review (with "What you see is what you get").
|visualTranslation / visualReview||no|
|File||*.xsl||Xml files in the directories "proofRead" and "alignLayout" can contain an xml-type reference to an xsl file, that is able to transform the XML to a layouted HTML version. This reference to xsl can either be an http(s) link or can be a path relative to the xml file pointing to an xsl file within the zip package||visualTranslation / visualReview||no|
|Directory||alignLayout||Similar to the concept of a pivot language it is possible to use an aligned XML with a referenced XSL stylesheet (see above) as source for the visual review. This XML will be aligned to a matching bilingual file in the proofRead folder, meaning that it is expected to hold the same segments (what is validated). The filename of the aligned layout must be identical to the bilingual that contains the same contents, except the fileextension. So "xyz.xml" matches "xyz.xml.sdlxliff" and it also matches "xyz.sdlxliff" and "xyz.xml.mxliff" or "xyz.mxliff". The aligned XML must be provided in a folder "alignLayout" and define a stylesheet via processing instruction as described above. It is possible of using multiple aligned XML/XSLT files for multiple bilingual files in "proofRead".||visualTranslation / visualReview||no|
|File||*.tbx||Contains 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|
|File||QM_Subsegment_Issues.xml||Contains 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|
|File||task-template.xml||Contains a task template. Can be used to configure translate5 in an task-specific way.||no|
Only for import packages, that contain STAR Transit NXT files.
The file itself can be empty. It is a flag file.
|File||*.bconf||This 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 seamlessly 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||no|
|File||pixel-mapping.xlsx||This optional file can be provided to define the pixel-length for a pixel-based length check in translate5. It defines the pixel-width for each character of a font for a certain font-size.||no|