After segmenting a specific source XLF or XLIFF file using an XLIFF 1.2 file type configuration (including the Default one) and opening the task in Online Editor, the target file creation fails with the following error:

An error occurred while saving the asset into AIS. Details: com.idiominc.wssdk.asset.WSAssetSegmentationException: There was no XML start tag open.

This error occurs under the following scenarios:

1- When opening the task in Browser Workbench after it has been opened in Online Editor.

2- When exporting the task, previously opened in Online Editor, to a WSXZ package. The export is successful, but after opening the WSXZ package in Trados Studio, attempting to create a target file results in the same error.

3- If the error in scenario #2 is ignored in Trados Studio, or if the translator does not attempt to generate a target file (which should always be done), they may not become aware of the error. If they then create a WorldServer Return package, the package will fail to import/upload to WorldServer with the same error message.

The Online Editor corrupts the bilingual file cache, causing an error when trying to create a target file.

Until the defect is fixed, the workaround is to avoid opening similar XLIFF files in Online Editor at any point during the translation process.

Or - if possible - remove the content associated with the ept tags from the source XLIFF file and re-submit to a new project.

Something in the content of the source XLIFF file causes corruption, leading to an error when generating a target file if the task is opened in Online Editor.

The content causing the issue are the ept tags, for example:

<ept id="2">&lt;/strong&gt;</ept>

Removing them from the source XLIFF file will prevent the isue from happening after opening the task in Online Editor.

This issue has been filed as defect CRQ-41573.