• Show convenient version of this site
  • Deutsch
  • English
Contact
Newsletter
  • Products
    • ALS
      • Across Language Server
        • Translation Management
        • Terminology Management
        • Translation Memory
      • Editions
      • Interfaces
    • ATE
      • Across Translator Edition
      • Editions
      • Download
      • Across Account
    • Elanion
      • Overview
      • Login
  • Solutions
    • Customers
      • Enterprises
      • Language Service Providers
      • Translators
    • Industries
      • E-Commerce & Trade
      • Pharmaceuticals & medicine
      • IT & Software
    • Departments
      • Marketing & E-Commerce
      • Technical Documentation
      • Software User Interfaces
  • Services
    • Hosting
    • Training
    • Consulting
  • Partners
    • Language Service Providers
    • Universities
  • Company
    • Across Systems
    • News
    • Events
    • Career
    • Contact
  • Knowledge
    • Blog
    • Video Library
    • Case Studies
    • White Papers
    • Fact Sheets
    • File Formats
    • Expert Features
  • Support
    • Online Help
    • FAQ
    • Support Request
    • Updates
    • New Functions
Schedule Consultation

Configuring the QM criterion of the crossTerm check

The QM criterion of the crossTerm check verifies whether the source-language terms (source terms) in the source text have been duly translated with the corresponding target-language terms (target terms).

The terminology check is only applied to terms that appear in the source text and that are stored as terms in crossTerm. For this, at least one source-language term and a corresponding target-language term must be stored in crossTerm. If crossTerm does not contain any target-language term, the crossTerm check will not report any error. In addition, the stopwords are not taken into account by the crossTerm check.

Moreover, the check is conducted at paragraph level. Therefore, a target-language term does not need to exist in a certain sentence. Rather, it is sufficient for the respective term to be used in the paragraph.

The function of the crossTerm check can be customized as needed. By default, the crossTerm check verifies whether any existing target-language terms in crossTerm were used to translate the terms in the source paragraph. If a target-language term was not used, the criterion reports an error for the respective paragraph.

However, the crossTerm check can also be customized for more specific checks. For example, the translation can be checked for the use of forbidden terms. The crossTerm check can be configured under Tools > System Settings > General > Quality Management v6.3.

You can configure the crossTerm Check as follows:

The Option Source Terms to be Checked

Using the drop-down list, you can determine which source-language terms the subsequent terminology check is to be conducted for. Target language terms will only be searched for and checked for in connection with terms found in the source text on the basis of the selection made here (see following options Terms to be accepted).

You can select one of the following options:

Option
Description
All
The check is conducted for all terms contained in the source text.
All but "Do not use"
The check is conducted for all terms contained in the source text except for terms defined as DoNotUse terms. By default, these are displayed with the icn_cDesk_cTerm_unwort icon in crossTerm and in the crossTerm window of crossDesk.
Recommended only
The check is only conducted for Recommended terms in the source text. By default, these are displayed with the icn_cDesk_cTerm_vorzugsbenennung icon in crossTerm and in the crossTerm window of crossDesk.

The Option Target Terms to be Accepted

In addition to the selection made above, the target-language terms to be accepted during the check can be defined with the option Target terms to be accepted. Thus, the crossTerm check will not report these as errors. In contrast, target-language terms that do not correspond to the selected setting will be reported as terminology errors.

You can select one of the following options:

Option
Description
All
As a matter of principle, the crossTerm check will accept any target-language term used in the translation for a source-language term, regardless of whether such is labeled as Do not use or Recommended. Even if no usage attribute was defined for a target-language term used, the term will be accepted and will not be considered a terminology error.
An error will only be reported if a target-language term is not used for a source-language term even though such a term is available in crossTerm. If there are several target-language terms for a source-language term, only one of these terms needs to be used in the translation.
All but "Do not use"
In this case, the crossTerm check will accept any target-language term used in the translation except for terms defined as "DoNotUse" for a source-language term (see Source terms to be checked).
Thus, an error will be reported if a "Do not use" term is used for a target-language term although a "Recommended" term was available. Moreover, a terminology error will be reported if a target-language term is not used in the translation although such a term exists in crossTerm with the Recommended attribute or without any usage attribute.
Recommended only
If this option is selected, the crossTerm check will only accept terms defined as Recommended for a source-language term (see Source terms to be checked). If there are several recommended target-language terms for a source-language term, only one of these terms needs to be used in the translation.

Further options

Additionally, you can use the following options:

Option
Description
Only consider terms of the same server context
By means of this option, you can determine that during the crossTerm check, only terms that match the server context of the current project are to be taken into consideration. Under employment of crossGrid, the server context designates the data stock of a Master Server or a Trusted Server. If, for example, the source text contains a term that originates from the own server context, but the current project has been delegated by a Master Server and therefore originates from another server context, the term used in the source text will not be checked.
Only consider terms matching the relation of the current project
By activating this option, you can determine that the crossTerm check should only check terms whose relation matches that of the current project. If, for example, the current project is assigned the relation A, but the relation B is set for a source-language term, the term will not be checked if the option is activated.
Only consider released terms
With this option, you can determine that the crossTerm check should only check terms that have been released, i.e. terms with the Released state. Thus, unreleased terms will not be checked.
Register for our Newsletter now

Our newsletter provides you with exclusive news about the Across Language Server, often even before the official announcement. The newsletter also provides you with early information on events, webinars, and training sessions.

  • Legal Notice
  • GTC
  • Privacy Statement
  • Cookies
  • info@across.net