XLIFF 2.0 Filter Config Options
The Enterprise XLIFF 2.0 Filter Configuration offers several options beyond the XLIFF 2 specification. Please see below for a list of enhancements.
Enhancements
- If a unit has canResegment="yes" and the config option needsSegmentation.b=true is set, linguistic segmentation is applied to the content as if it were a paragraph. XLIFF 2.0 assumes all unit content is pre-segmented and are sentences. Generally XLIFF 2.0 segmentation can be changed (split/merge for example) but there is no specific option in the standard to mark the content as a paragraph. For more information, click here.
- The config option simplifyTags.b=true directs the system to not simplify inline codes. Otherwise ending and trailing codes are trimmed and any consecutive codes are merged to simplify the presentation to the translator.
- The config option mergeAsParagraph.b=true directs the system to forget any segmentation applied with needsSegmentation.b=true and merges the unit as one, single segment. This option is useful when the original segmentation is needed, not the segmentation introduced by Enterprise.
- The config option useCodeFinder.b=true allows regular expression based rules to be written that convert text into inline codes and protects these codes from translation in the workbench. For example, emoji substrings can be supported using custom codefinder rules. On merge the XLIFF wrapper elements are removed and only the original (protected) content remains.
- The option maxValidation.b=true enables stricter XLIFF 2.0 schema checking and reports errors to the user assuring compliant files.
