Terminology: Frequently Asked Questions (FAQ)
- 1 Introduction
- 2 Questions and answers
- 2.1 Why are there discrepancies between the total number of terms in the search list and an export/import file?
- 2.2 Is it possible to generate and extract terminology for all projects for a specific client at once?
- 2.3 Why is terminology not applied when machine translation (MT) is used?
- 2.4 Why is a terminology search at XTM Workbench level limited to a single XTM Cloud customer?
- 2.5 Can the LSP have access to the terminology resources of the contractor’s client (contractor’s contractor)?
- 2.6 Where can I add forbidden/rejected/not approved terms?
- 2.7 How do I remove duplicated terms?
Introduction
This article is intended to answer common questions about the Terminology module in XTM Cloud, or help resolve issues you might experience with it.
Before reading the article below, make sure you have a good understanding of how the Terminology module works. For details, see the thematic articles contained in the Terminology section! |
|---|
Questions and answers
Why are there discrepancies between the total number of terms in the search list and an export/import file?
The terminology search works as a filter. When you add the translation language to the search, it simply places that language at the top of the search results list. However, terms with other target languages are also displayed. Otherwise, the translation languages are in alphabetical order.
Without translation language:
With a translation language (Japanese):
You will only see the total number of reliable terms in the Import or Export tab screens (in which you import or export terminology files). That is because you can specify just the translation languages and exclude other target languages.
Is it possible to generate and extract terminology for all projects for a specific client at once?
Currently, it is not possible generate and extract terminology on multiple projects at once. It is only possible at project level and only when the Run Terminology extraction option is selected during project creation in XTM Cloud.
Why is terminology not applied when machine translation (MT) is used?
Machine translation (MT) is a separate tool from the Terminology module. In machine translation, segments are translated according to the MT engine in use. After machine translation, it is up to the user to change (post-edit) a translation when necessary. The terminology itself merely constitutes a clue for correcting the translation, which must be performed by a Linguist. XTM Cloud is not responsible for the way in which the MT engine supplies the translation, nor can XTM Cloud exclude part of a segment from translation.
Bear in mind that terminology is only for informational purposes, for the users. Terminology and MT are two separate engines that do not work together.
Why is a terminology search at XTM Workbench level limited to a single XTM Cloud customer?
This behavior is correct and will not be changed. When a user with the Terminologist role opens the terminology in XTM Workbench, it will only show one XTM customer (the customer for which the project was created). It will not include the customers specified in the Settings when the project was created. For instance, the customer TestCustomer is the one under which the project is created, in the screenshot below. This is the only customer whose terminology will be contained in the scope of the search.
Can the LSP have access to the terminology resources of the contractor’s client (contractor’s contractor)?
Currently, this is not possible. Only an LSP that has a direct connection to a particular contractor can have access to that contractor’s terminology resources. Even then, they can only do so if that is specified in the LSP’s access rights, in the Terminology sections, on the contractor side [Users → LSPs → (select an LSP) → LSP Editor → Access rights].
Sample LSP chain connection: Main contractor → LSP1 → LSP2.
The contractor can have access to LSP1’s terminology resources, and vice versa, but not to LSP2’s terminology resources.
LSP2 can have access to LSP1’s terminology resources, and vice versa, but not to the main contractor’s terminology resources.
Currently, due to security considerations, there are no plans to modify the existing behavior. Altering this setup could potentially compromise security. It is important to note that the contractor might not be aware that their translation content is handled via a third-party agency (LSP2) and they might not consent to any configuration changes that might impact their terminology resources.
Additionally, it is crucial to recognize that the contractor is exclusively linked to one LSP and their access permissions might vary depending on the policies of that specific LSP. The LSP might or might not grant access to certain functionalities.
Where can I add forbidden/rejected/not approved terms?
Forbidden/rejected/ not approved terms can be added to the terminology by a user with the Terminologist role who is also able to add them. They can do so in the XTM Cloud UI. Select Terminology → Manage. In the Manage tab screen, select the Status dropdown for a particular term to select its status:
How do I remove duplicated terms?
The only possible way to remove duplicated terms is to export all terms, filter all concepts and remove duplicated terms from the file. Then, delete all the terminology that has been just exported from the XTM Cloud UI and reimport the corrected file again.
To learn about the terminology import and export process, we recommend that you read the following how-to articles: