| Table of Contents |
|---|
| Page Properties | ||
|---|---|---|
| ||
Introduction
What is XLIFF:doc status?
...
NAME IN XTM | NAME IN TIPP |
|---|---|
1:New | new |
2:Translated | translated |
3:Proofed | final |
4:Validated | signed-off |
-1:Rejected | needs-review-translation |
...
Locking segments in XTM Workbench with a particular XLIFF:doc status
XTM Cloud allows for locking segments in XTM Workbench with a particular XLIFF:doc status in the XTM Cloud UI.
First of all, as a user with administrative privileges, you need to enable locking segments with a certain status globally in the UI (Configuration → Settings → Translation → TM → Matches - general → Mark segments as locked when).
...
At the project creation stage (and in the settings of the XTM project template) you can then choose the XLIFF:doc status that will constitute basis for locking a segment containing that status, in XTM Workbench, by selecting one of the following values from the Mark segment as locked dropdown:
Xliff:doc status >= Translated,
Xliff:doc status >= Proofed,
Xliff:doc status >= Validated.
...
Update of XLIFF:doc statuses and its implications
...
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.  |
|---|
...
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:
...