Versions Compared

Old Version 21

changes.mady.by.user Damian Rozmiarkowski

Saved on

compared with

New Version Current

changes.mady.by.user Damian Rozmiarkowski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

IMPORTANT!

Keep in mind that it is not possible to discriminate between types of inline tags tag that are grouped when using this option. All inline tags will always be grouped regardless of their type. For example:

  • span tag (e.g. span class="uitext">),

  • variable tag (e.g. <span class="uitext"><MadCap:variable name="flvar-product.SC" />).

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).

...

  1. 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 a

      • Segment 2: sunny day.

  2. 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:

  1. 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.

  2. 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.