Visit this page for example ZIP import packages.
Please note: translate5 project strives to support the TIPP format as import and export format. Any kind of support for this development is welcomed.
File structure of an import package
Type | Name | Usage | 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. 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 |
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. | 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. | no |
File | task-template.xml | Contains a task template. Can be used to configure translate5 in an task-specific way. | no |
File | DEU-ENG.transitConfig | Only for import packages, that contain STAR Transit NXT files. The file itself can be empty. It is a flag file. | no |
Usage hints
- Folders and files mentioned in the above package structure MUST reside on the top level of the zip file (NOT inside some sub-folder).
- SDLXLIFF, openTM2 XLIFF and CSV-files can be mixed inside the proofRead folders an any needed way. STAR Transit NXT files have to be in a separate import package.
- Please use only ASCII characters in file or directory names and no special characters or German "Umlaute".
The Zip format does not provide any information in which encoding your operating system has saved a file or directory name. Due to this lack of the ZIP standard, it might cause errors inside translate5, if you do use file or directory names with NON-ASCII characters. Only exception to this rule: Your file system does use UFT-8 encoding (like Linux and Mac do).