| Table of Contents |
|---|
...
What should (or should not, if that is the case) be translatable; for example, columns in an Excel file, XML nodes, etc.
What files will be used for projects using this configuration or, more specifically, which file extensions? Examples: XLSX, DOCX, XML.
The URL you are using to access XTM Cloud and the company name used during the login process.
Where should the configuration be set up? Should it be a filter template, a customer-specificconfiguration, or set up globally for all the customers? Remember that there is a configuration hierarchy within XTM Cloud (for details, click here for more information).
EXAMPLE:
Case: There is a configuration set globally that, in Excel files, column “A" is not to be extracted for translation. Result: The "A" column will not be translated. Case: Given the customer’s “Test customer” configuration is defined as having the "A" column translatable. Result: The "A" column would be translated in projects for this customer, but not in projects for other customers. Case: Given the filter template configuration to translate column "A" cells if the "B" column contains the word "translate" next to the cell, and we use this filter template for the project. Result: All the cells in column "A" with the word “translate” in column "B" will be translated. |
Provide the XTM International Support team with examples of source files that are meant to be used with the new configuration. Having example source files provided has proven to greatly speed up the configuration development process.
If the new configuration would be similar to an existing one, but with changes, tell us so. When this information is provided to us, we can understand the basis of the presented issue more deeply and understand what the expected outcome is much more quickly.
...