ZIP import package format

workfiles

(proofRead is deprecated)

visual

(visualReview is deprecated)

More information about the visual plug-in of translate5 (paid plug-in, only viewable for users with appropriate rights)

The contained files are used to generate a layout for visual translation or visual review (with "What you see is what you get").
Possible contents of the directory visual are:

• A file "reviewHtml.txt", that contains one or multiple URLs (one URL by line and nothing else). The order of the URLs should be the same as the order of the corresponding files in workfiles.
• OR: A number of PDF files OR HTML files (mixing PDF with HTML is currently not supported - please contact translate5s developers, if you need this)
  
  • The PDFs / HTMLs contain the same text as the text that is contained in the files in the workfiles directory.
  • If the workfiles directory contains bilingual files, the PDFs / HTMLs can either be in source or target language
  • if the PDFs / HTMLs are in the target language, the import option "Connect layout to" should be set to "target"
  • The order of the PDF / HTML files on the file system should be the same as the order of the contents in the workfiles directory. Yet it is not necessary that the PDFs / HTMLs are the same number of files or have the same file names.
  • The naming of the files in the visual folder does not matter at all. Only their order should reflect the order of the contents in the workfiles folder.
  • multiple PDFs are merged to a single PDF and result in a single review file containing several pages/chapters whilst multiple HTML files or downloaded URLs will be accessible through a pager in the frontend
• OR: A number of XML/XSL combinations.  These combinations will be processed to HTML files which then will be used as the visual source as described above. This incorporates the standard, text-based segmentation and thus these XML/XSLT files are not aligned to the bilingual files in the "workfiles" folder like when adding XML/XSL via the "alignLayout" folder (see below). The stylesheet(s) have to be in the /visual folder as well and must be referenced with a XML preprocessing instruction e.g.  <?xml-stylesheet type="text/xsl" href="stylesheet.xsl"?>

More information about the visual plug-in of translate5 (paid plug-in, only viewable for users with appropriate rights)

Subdirectory in /visual. If a Video is supplied here, a visual video can be generated. Only in conjunction with a workfile with timecodes, that connect the segments to frames in the video, which currently must be a .xslx or .srt file. The prequesites are:

• Video: Filetype mp4, codec h264, max. size 250MB, max. Resolution FullHD (1920x1080), max. Bitrate 1MB/s
• Excel Workfile: Filetype xslx, 3 columns, first column "Timecode from", second column "Timecode to", third column "Segment text"; The first row may be a header row "from", "to", "text"
• SRT Workfile: SubRip subtitle file, filetype srt as defined here: https://en.wikipedia.org/wiki/SubRip
• Supported Timecode formats; The timecodes in the workfiles must be in one of the following formats: "HH:MM:SS:FF", "HH:MM:SS,mmm" (srt), "HH:MM:SS.mmm" (vtt) or "v" (plain milliseconds)

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.