XLIFF Joiner Step

From Okapi Framework
Jump to: navigation, search

Overview

Re-joins multiple XLIFF documents into one or more documents (see Input file marker parameter). The first document of the naming pattern group provides content up to the first <file> element and after the last <file> element. The step then grabs the <file> elements from subsequent documents and any content between multiple <file> elements. To split a single XLIFF document into several ones, use the XLIFF Splitter Step.

Note:

  • Because of the sequential processing of files in the pipeline the files are joined in the order they arrive in the pipeline, regardless of the index number added by the XLIFF Splitter Step.
  • Subsequent documents of the same naming pattern group ignores content before their first <file> element and after their last <file> element. This is because the XLIFF Splitter Step writes out this content for each document.

Takes: Raw documents. Sends: Raw document.

The received event is unaltered. The step outputs one or more output XLIFF documents depending on the input filenames pattern.

Parameters

Input file marker — Enter the marker text that is to be used to process files with similar naming pattern(s).

Output file marker — Enter the marker text that is to be used to generate the filename(s) of the output file(s). If files with the same names already exist in the output directory, they will be overridden without warning.

For example, with the following input parameters:

   Input file marker: _PART
   Output file marker: _CONCAT
   Input file list: C:\Project\FolderABC\File1_PART001.xlf
                    C:\Project\FolderABC\File1_PART002.xlf
                    C:\Project\FolderABC\File2_PART001.xlf
                    C:\Project\FolderABC\File2_PART002.xlf
                    C:\Project\FolderABC\File3.xlf

You get the following output files

   C:\Project\FolderABC\File1_CONCAT.xlf
   C:\Project\FolderABC\File2_CONCAT.xlf
   
   C:\Project\FolderABC\File3.xlf -> Skipped file, the filename does not have the expected marker "_PART".

Limitations

None known.