| Table of Contents |
|---|
| Page Properties | ||
|---|---|---|
| ||
...
| 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:
|
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).
Which file formats can XTM Cloud process?
Visit the following XTM Cloud help page, to see what file formats are supported, for translation in XTM Cloud: Language codes (select your XTM version and search for the phrase: Language codes).
What should I do if the target file fails to generate or does not look as expected?
...
What should I do if the target file fails to generate or does not look as expected?
If the target file fails to generate or does not look as expected, this could be for several reasons. One common issue is the misplacement or lack of inline tags, which can cause target file generation to fail. To troubleshoot this, you can check if XTM Cloud is able to provide a reason for the failure by selecting Project Editor → Files → (select the relevant target language) → Target → (click on the red exclamation mark icon). If the message does not tell you what is wrong with the file, you can create a simple TEST project that is exactly the same as your original one and try to generate the target file there. If the target file still has the same problem, you should also check for any misplaced inline tags and try again.
...
Yes, XTM Cloud can localize plurals in several file formats including Android XML, DITA files, JSON with ICU syntax, PO/POT and stringdict. However, by default, plural localization is disabled. Plurals are grouped in keyword categories for naming forms: zero, one, two, few, many, and other. The other form is always required as it is used for something that does not match any other category.
...
To find out more about processing plural forms/ICU plural syntax by XTM Cloud, read the following articles:
How do I use a filter template in a project?
...
See the article that describes the process of creating a filter template via the UI: How to create a filter template in the XTM UI and apply it to a project.
Also, make sure to visit the official XTM Group documentation, for even better comprehension of the subject: Configuring custom variables in a new template at Project level.
...
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.
Why are there so many green inline tags displayed in the source segments for a particular file in XTM Workbench?
Sometimes you might experience a great number of green inline tags displayed in the source segments for a particular file in XTM Workbench. In the vast majority of cases, when you go to the { } Inline tags section of the docked panel, what you might observe is that those green inline tags are related to the so-called Spacing.
...
On the XTM Cloud side, there is not much that can be done with the said inline tags. One of the core principals of file processing in XTM Cloud is to maintain file structure consistency between the source and target files. Therefore, the tags in the source file must also be included in the target file.
The source of these inline tags are differences in spacing. A lot of different spacing mostly occurs when source files are converted from some other extensions, such as PDF.
Therefore, the best solution to reduce the number of tags is preprocess files and standardize spacing.
Why do my source files fail at analysis although the format is supported in XTM Cloud?
Sometimes, you might experience that source files, whose format is fully supported by XTM Cloud, are not being analyzed. In the vast majority of cases, the issue stems from a faulty filter template that you might have applied for a project. To validate that, try creating a new project with the source files in question and without applying the said filter template, to see if the files will be analyzed successfully.
| Info |
|---|
You can also deselect a filter template in an existing project, in Project Editor → General info → General info → Filter template. Bear in mind though that such action will require project reanalysis, about which you will be informed by a pop-up message.  |
In both cases, when the filter template turns out to be the cause of the issue and when it does not, do not hesitate to contact the XTM International Support team and provide details. The team will investigate the filter template’s configuration.
Why is some part of the source text from a MS Word file not being extracted for translation in XTM Workbench?
For MS Word files, there might be several reasons why certain part of the text is not being extracted in XTM Workbench although the text in question is clearly visible in the source file. In the vast majority of cases, the issue is caused by application of certain styles that prevent the content from being sent for translation in XTM Cloud.
...
For example, the affected text might be marked with the Hidden option used in its chosen style.
Since the font is marked as Hidden, the text is excluded from translation by default.
If these rules need to be adjusted, you should consult it with your administrators and create an official JSM request to prepare a relevant configuration that will allow this text to be extracted for translation in XTM Cloud.
Alternatively, you can modify this style to remove the Hidden option effect, or change the style applied to this text.
To learn more about what is and what is not extracted for translation in MS Word files, make sure to read the following section of the dedicated article: How are segments in MS Office files (Word, Excel, PowerPoint) extracted? -> Word – .doc, .docx, .rtf.
Are language codes translated in HTML file format?
In some file formats (XLIFF, XLF, DITA, DITAMAP), there is a standardized way in which language is declared. XTM Cloud then replaces a source language code with a target language code in target files.
However, HTML format does not belong to that group. Therefore, XTM Cloud does not do anything to language codes in HTML files. Also, those language codes are not extracted for translation in XTM Cloud.
Can I translate XML format in accordance with existing language codes, and then receive 1 file with, say, 12 translations?
This is what XTM Cloud considers a multilingual processing of a file. Currently, it is only possible to process XLSX files as multilingual. The XML format can only be processed as containing a single language.
See other file formats which can be processed for more than just one language:
XLIFF/XLF → bilingual,
TMX → bilingual,
TS (Digia QT) → bilingual,
As a workaround, a special configuration can be prepared by XTM International Support to only extract one of the languages for translation from XML format. This, however, would require you to preprocess and postprocess the file, or have multiple configuration versions.
What file formats does XTM Cloud support?
If the file is not on the supported files list, and it is not XML-based, XTM Cloud does not support it. If the file is similar to one of the supported file formats, or is a simple text-based file, our XTM International Support can whether or not a proper configuration can be prepared.
Visit the following XTM Cloud help page, to see what file formats are supported, for translation in XTM Cloud: File formats supported in XTM Cloud (select your XTM version and search for the phrase: File formats supported in XTM Cloud).
Do multilingual Excel features also work for CSV files, since XTM Cloud processes CSV as Excel?
CSV files can be processed as bilingual in a very limited way. Therefore, converting them to XLSX format is recommended, to get more multilingual features. Bilingual CSV does not import translations from the source file, but can return translations to a different column.