Salesforce

How to set up a XLF/XLIFF Filter Configuration for target segment only in earlier versions of WorldServer

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer before 11.1.1
Symptoms/Context
In WorldServer 10.4.x until 11.1.0, when I segment a source XLF or XLIFF file I get a segmentation error stating that this file format is not supported. Is it possible to create a filter configuration that I can use to segment my XLF/XLIFF file?

Or: the XLIFF 1.2 File Type does not segment my XLF/XLIFF file as expected. Which other file type and configuration can I use?
Resolution

The XLIFF format is natively supported starting from version 11.1.1, as stated in this article. In earlier WorldServer versions (until 11.1.0), a filter configuration could be created, based on certain conditions.

The solution is based on using the Custom XML (Legacy Embedded Content) File Type. A specific Filter Configuration based on this filter should be created. The filter configuration includes these 2 entries in the ‘parser’ section:

//target always translatable
//* not-translatable


Note: The order of the 2 entries matters

IMPORTANT: If the XLF/XLIFF Mime Type is not set in WorldServer (which is not per default), this Mime Type should first be added to the Mime Types table under

Management > Administration > Customization

and it should be mapped to the Custom XML Studio File Type filter and filter configuration.

Note: This filter configuration applies to most XLF/XLIFF files. However, if the XLF/XLIFF files have a different structure and cannot be segmented correctly with the Filter Configuration above, please contact the RWS Professional Services Team for a quote for the creation of a custom filter.

 

Root Cause
In earlier versions, WorldServer did not provide an Out-of-the-Box filter configuration to address this need. The XLF or XLIFF file format is not supported. The support has been introduced starting from WorldServer 11.1.1. This article addresses a workaround for earlier versions or in case the XLIFF 1.2 File Type does not work as expected.
Reference
This article is relevant.
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by