Sometimes, if a Linguist uses a different CAT tool instead of XTM Cloud, some segments in the translated files automatically display additional inline tags or some tags are missing, while these tags are complete and placed in the correct positions, in the XTM Cloud project.

In memoQ, you might for example see:

Open

If you are wondering why the inline tags have disappeared, it is because, in XTM Cloud, when you use a normal inline tag that has no content, it will be transformed into a self-closing tag during target file generation.

In XTM Workbench, a normal inline tag can represent text formatting such as bold or italics, non-translatable technical symbols such as HTML tags or other special characters. They are displayed as numbers in curly brackets.

According to the documentation for the XLIFF file format (XLIFF 1.2 Specification), a normal inline tag is changed into a self-closed tag in this situation:

This means that even if the <g> element itself has become self-closed tag due to not having any content, it should still be interpreted as an opening and closing tag by any CAT tool that interprets XLIFF files.

Sometimes, other CAT tools might struggle to process self-closed tags, even though these tags are valid and supported correctly in XTM Cloud. This is because self-closed tags adhere to both the XLIFF and XML standards. The issues encountered in other CAT tools are related to their individual capabilities and the way they interpret tags. Each CAT tool might have its own way of interpreting and handling XTM files.