Contact
Newsletter
Schedule Consultation

QM Criteria (QM v7.0)

Tip
Tip

An overview of the QM criteria and options that are enabled by default is available here.

.NET resources

  • Comprises the following options:
  • Check for overlapping controls

    If two controls overlap, an error will be displayed.

  • Check if text exceeds element size

    If the text does not fit into the control, an error will be displayed.

Spacing

  • Comprises the following options:
  • Check consecutive whitespaces

    Checks whether the document paragraph contains any consecutive whitespaces.

    For this criterion, the filter for similar errors groups errors with the same whitespaces order.

  • Ignore if same sequence is used in source
  • Check tabs

    Checks the consistent use of tabs in the source and target paragraphs.

    For this criterion, the filter for similar errors groups the following error types:

    • Different use of tabs in the source and target paragraphs
    • Tabs missing in the target paragraph
    • Additional tabs in the target paragraph
    • Different tab/whitespace order in the target paragraph
  • Check bounding spaces

    Checks the consistent use of whitespaces at the beginning and end of a paragraph.

    For this criterion, the filter for similar errors groups errors with different leading and trailing whitespaces.

  • Check consistency of spaces around placeables

    Checks the consistent use of whitespaces before and after placeables in the source and target paragraphs. If the position of the placeables is different in the target text, e.g. if the placeable is located at the beginning or end of the sentence in the target text, this will be taken into consideration, and no additional (unnecessary) space will be inserted.

Date/time/numbers

Checks whether the date, time and number formats have been translated correctly and adapted to the target language according to the settings under Tools > System Settings > General > Language Settings.

Tip
  • Notes
  • The criterion can only identify errors in the translation if Across recognizes the particular date, time, or number in the source text as such. For these data to be recognized, they must have a valid format in the source text.
  • For example, a date correctly recognized by Across is evident from the blue overline.
  • The tooltip of a data, time, or number shows what format the information was recognized as and what the corresponding information looks like in the target language.

Example

  • In the language settings, the date formats have been defined as follows:
  • English: YYYY-MM-DD, e.g. 2019-05-31
  • German: DD.MM.YYYY, e.g. 31.05.2019

If, for example, the date 2019-05-31 in the English source text is translated into German as 2019-05-31, the QM criterion will report an error.

Formatting

Checks whether all formatting (such as boldface and italics) used in the source paragraph has been used in the target paragraph.

  • Comprises the following options:
  • Check formatting order
  • Warn if rich text formatting is used in target
  • For this criterion, the filter for similar errors groups the following error types:
  • Source paragraphs have the same formatting, but formatting is missing in the target paragraphs.
  • Source paragraphs have the same formatting, but additional formatting exists in the target paragraphs.

Capitalization

Checks whether the uppercase/lowercase spelling of the first word of a target paragraph corresponds to that of the first word of the source paragraph. If, for example, the first word in a source paragraph starts with a lowercase letter, but the first word in the target paragraph starts with an uppercase letter, the QM criterion will indicate an error.

Identical segments

Checks whether segments in the source and target paragraphs are identical and will report an error if this is the case.

  • Segments that only consist of the following elements are not taken into consideration:
  • Numbers
  • Punctuation marks such as . , : ! ? + * % etc.
  • Placeables
  • Spaces

Same source – different translation

Checks whether identical source text segments have been translated differently.

Brackets

Checks whether the number and type of brackets used in the source and target paragraphs are consistent under consideration of the language.

  • The criterion takes into consideration the following brackets:
  • ()
  • []
  • {}
  • <>

The order of the use of brackets in the translation is not checked, as it may differ from the source text.

For this criterion, the filter for similar errors groups errors in which the brackets differ in the same way in the source and target paragraphs.

Empty target

Checks target paragraphs for missing translations and reports an error if a target paragraph is empty, but has the editing state Touched or Translated.

Tip

Any target paragraphs that are left empty will also remain empty in the checked-out document. A paragraph reported as an error might have been left empty on purpose. Check whether the reported errors need to be corrected or can be ignored.

Placeables

Checks if the placeables, inline elements, and any XLIFF elements used in the source paragraph have been used in the correct number and, optionally, in the correct order and with the same formatting in the target paragraph.

Tip

The criterion merely checks the number and order of the placeables/elements used and does not consider factors such as the position of text that may exist between the placeables/elements.

For this criterion, the filter for similar errors groups errors in which the same placeables or elements were used.

Private Use Area characters

Checks whether all Private Use Area characters used in the source and target paragraphs are identical and exist in the same number.

Tip

The Private Use Area is a special Unicode area that enables the use of custom characters not standardized in Unicode. These characters must be coordinated between the parties that create them and those who use them. For example, Private Use Area characters can be provided in a jointly used font file.

For this criterion, the filter for similar errors groups errors with the same missing and additional PUA characters.

Spelling

Checks the spelling in the target paragraph using the modules selected under Tools > User Settings > General > Spell-check. Optionally, you can determine that no errors are to be reported for words that occur in the same way in the source paragraph.

End punctuation

Checks whether the number and order of the punctuation marks are identical in the source and target paragraphs.

  • The criterion takes the following punctuation marks into consideration:
  • .
  • ,
  • :
  • ;
  • ?
  • !
  • ...

For this criterion, the filter for similar error groups errors in which the sentence delimiters differ in the same way in the source and target paragraphs (e.g. all paragraph pairs with ; in the source paragraph and , in the target paragraph).

Segment count

Checks whether the number of segments in the source and target paragraphs are identical and will report an error if this is not the case.

Terminology

Checks whether the source-language terms (source terms) in the source paragraph have been duly translated with the corresponding target-language terms (target terms). An error will also be reported if a do-not-use term occurs in the target paragraph.

  • Comprises the following options:
  • Use stemming

    Applies to source terms only; stemming is always activated for target terms.

  • Only consider released terms
  • Only consider terms of the same relation as the current project

Display text bounds

Checks whether the length restrictions for display texts are complied with in the target text.

Translation memory

  • Comprises the following options:
  • Unused 100% Match

    Checks whether all 100% matches from crossTank have been used in the translation.

    If there are several 100% matches for a sentence, only one of the available 100% matches should be taken over in the translation.

  • Unchanged fuzzy match

    Checks whether a fuzzy match was inserted in the current paragraph but not edited. This criterion checks all matches that are above the match rate you defined under System Settings > General > Project Settings Templates > crossTank > Pre-translation.

    For this criterion, the filter for similar errors groups errors with the same source text.

  • ##NO_MATCH## placeholder

    Comprises all target paragraphs containing the pre-translation placeholder ##NO_MATCH## at least once. Thus, this criterion makes sure that the translator does not forget to replace the placeholder with the respective translation.

    • The placeholder will be inserted in a paragraph
    • if the option Insert placeholders when not all segments can be pre-translated is enabled under Tools > System Settings > General > Project Settings Templates > crossTank >Pre-translation and
    • if crossTank does not contain 100% matches for every sentence of the paragraph.

Different source – same translation

Checks whether different source-text segments have the same translation.

Windows resources

  • Comprises the following options:
  • Check for overlapping controls

    If two controls overlap, an error will be displayed.

    An error will also be displayed if a control and a group field overlap. This applies if a control and a group field overlap and if a control from the associated group field was moved.

  • Check if text exceeds element size

    If the text does not fit into the control, an error will be displayed.

Repeated words

Checks the text for two successive identical words. The check is case-sensitive (except for the initial letter) and ignores numbers (which are part of the number consistency check). Repetitions that already occur in the source text are ignored.

Tip

For languages that use reduplication (e.g. Japanese), the use of this criterion might not be beneficial. If necessary, create a separate QM template without this criterion.

XML validity

Checks the translated XML document for validity. On the one hand, the well-formedness of the XML document is checked. On the other hand, the XML document is checked against the underlying document type definition (DTD) or XML schema definition (XSD) with which the XML document was checked in to Across. It is checked whether the rules defined in the DTD or XSD have been complied with.

Tip

In XML, a document is considered well-formed if it complies with the basic rules of the XML standard, e.g. the rules for correct tag nesting, the explicit declaration of entities (except amp, lt, gt, apos, quot), etc.

An XML document that is checked in to Across without DTD or XSD will only be checked for well-formedness.

If defined as a mandatory criterion, the validity check will be conducted automatically upon completion of a task. However, you can also start it manually with CHECK ALL in crossView whenever you wish.

The validity check is always applied to the entire target document. The check stops at the first error found in the document. After this error is corrected, the validity check can be repeated in order to find any other errors in the document.

Attention

If you ignore a validation error instead of correcting it, the validation check will not continue after the ignored error if you run it anew. Instead, it will again stop at the same position. This can even go unnoticed in case you have hidden ignored errors. Click icn_cView_qm_show-ignored to display ignored errors, correct the error, and run the validation check anew.