...
Inline tag grouping in XTM Cloud is a feature designed to minimize the number of inline tags displayed in a segment, so Linguists can concentrate on translation without worrying about tag placement. This feature is enabled by default and can be disabled globally, per file extension, without affecting TM matching, and does not require reanalysis.
| Note |
|---|
IMPORTANT! Currently, there is no option to enable/disable grouping tags at customer and/or project level. It can only be done at global level. |
Inline tags in XTM are grouped together by default if they are bundled together. If during an initial analysis a TM match that has inline tags is populated to the target segment and the tags position themselves in a way that does not satisfy the grouping mechanism, they will be ungrouped. However, once the tags are moved next to each other again in the XTM Workbench session, the criteria for grouping tags are then satisfied and so redundant tags are removed.Similarly, the hiding of leading and trailing inline tags is another feature intended to improve the translation experience. It can also be disabled globally, per file extension. Both features deactivate
| Note |
|---|
IMPORTANT! Keep in mind that it is not possible to discriminate between types of inline tag that are grouped when using this option. All inline tags will always be grouped regardless of their type. For example:
|
Similarly, the hiding of leading and trailing inline tags is another feature intended to improve the translation experience. It can also be disabled globally, per file extension. Both features deactivate automatically if the grouped or hidden inline tags inserted in a translation or match are in a different order from the source file. However, it is important to note that leading and trailing inline tags cannot be hidden in segments with internal matches (Repetitions and Fuzzy Repetitions).
...
Take a look at the following screenshot which presents two segments, the first of which (70) is actual content and the second one (82) is its alternate content.
...
For more information about the alternate content, see: How are segments in MS Office files (Word, Excel, PowerPoint) extracted?.
How does XTM process newline tags? What does it look like in XTM Workbench and can I decide where to put them in the target text?
When your source file contains a newline tag (\n), such as in the Today is a \n sunny day., in the XTM Workbench, this text will appear as: today is a sunny day. Here, the \n tag is displayed as a whitespace character.
By default, XTM Cloud does not break segments on newline tags. The entire text remains in one segment, with the newline tag rendered as a white space.
However, we can configure XTM Cloud to handle newline tags in other ways, based on your preference:
...
Break Segments on \n:
If configured, the \n will cause the text to be split into separate segments in XTM Workbench. For example:
Segment 1:
Today is aSegment 2:
sunny day.
Display \n as an Inline Tag:
...
second one (82) is its alternate content.
...
For more information about the alternate content, see: How are segments in MS Office files (Word, Excel, PowerPoint) extracted?.
How does XTM process newline tags? What does it look like in XTM Workbench and can I decide where to put them in the target text?
When your source file contains a newline tag (\n), such as in the Today is a \n sunny day., in the XTM Workbench, this text will appear as: today is a sunny day. Here, the \n tag is displayed as a whitespace character.
By default, XTM Cloud does not break segments on newline tags. The entire text remains in one segment, with the newline tag rendered as a white space.
However, we can configure XTM Cloud to handle newline tags in other ways, based on your preference:
Break Segments on \n:
If configured, the \n will cause the text to be split into separate segments in XTM Workbench. For example:
Segment 1:
Today is aSegment 2:
sunny day.
Display \n as an Inline Tag:
We can make the \n visible as an inline tag rather than displaying it as a whitespace character. This allows the linguist to see the newline explicitly and decide where to place it in the target segment, while translating the text in XTM Workbench.
Why are some elements/fields/tags that exist in my source file absent from the target file?
XTM Cloud should retain all elements/fields/tags that exist in the source file, regardless of whether or not they are eligible for translation in XTM Workbench. If you state that some nodes from your source file are missing in the target file that you generated in XTM Cloud, it means that there are two possible scenarios:
The data in question is absent from your source file in the first place, in which case you should double-check if this is truly the case. It might happen that clients overlook that fact when preparing source files for translation.
There might be an issue on the XTM Cloud side that would need fixing. In such a case, once you have made sure that your source file does contain the nodes in question, do not hesitate to contact the XTM International Support team and describe the problem.