| Table of Contents |
|---|
Introduction
...
To ensure that the TIPP package always has a unique response ID, it must always originate from XTM Cloud. In other words, the package must first be generated in XTM Cloud. It can only undergo further modification in another CAT tool and then be reuploaded to XTM Cloud. Otherwise the upload process is unsuccessful and the message shown below is displayed.   |
IMPORTANT!| Info |
|---|
TheXLIFF:docstatus does not influence TM matching prioritization in any way. However, such status can be used in TM penalty profiles, as one of the criteria by which TM matches can be penalized. |
...
To use XLIFF:doc statuses in XTM Cloud, we first need to enable the feature in Configuration → Settings → System → General → Enable TIPP (administrative privileges required!).
...
In Configuration → Settings → Translation → TM → Matches - general, there is an option called Do not store in TM segments with XLIFF:doc status set to Rejected, which, as the name suggests, causes all the TM records with the -1:Rejected status not to be displayed in TM database in the XTM Cloud UI.   |
|---|
Last but not least, the XLIFF:doc status can be changed in batch, during the workflow, by performing the Automatic step. We can specify the type of status to which we want to change the current statuses. To configure this step, go to Configuration → Settings → Workflow → Workflow steps (administrative privileges required!).
...
When we create a new project, the default XLIFF:doc status value for every segment is 1:New. Even if we enter a translation and confirm it, the translation is not changed immediately: we need to update the XLIFF:doc status manually, on the right-hand side of a particular segment.
If we create a second project that uses translation memory from the first project, its TM matches reflect the XLIFF:doc status from the original project, and:
...