QM Criteria for SGML, XML, and XLIFF files (QM v6.3)
Private Use Area Characters
Checks whether all Private Use Area characters used in the source and target documents are identical and exist in the same number.
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.
Tagged XML validity
Checks the translated XML document for its validity. On the one hand, the well-formedness of the XML document is checked. In XML, a document is referred to as well-formed if it complies with the basic rules of the XML standard, e.g. correct tag nesting. 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.
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.
Usually, the validity check does not start automatically, but must be started manually (e.g. via the context menu of the QM criterion in crossView). If the validity check is defined as mandatory criterion, it will take place automatically upon completion of the task.
An XML document that is checked in to Across without DTD or XSD is only checked for well-formedness.
In this example, the closing tag of the brand element has been omitted in the target-language paragraph. Therefore, the paragraph is not well-formed, and the document is not valid. Therefore, the QM criterion reports a QM error and an error message indicating the position of the error:
In this example, the QM criteria Tagged XML well-formedness, Placeables usage, and Placeables order also report a QM error, as the number of tags is different in the source and target paragraphs.
In the following example, the document is not valid because inline tags whose use in the current paragraph is not provided for by the utilized DTD were inserted in the target text. Therefore, the QM criterion reports a QM error and an error message indicating the position of the error:
Tagged XML wellformedness
Checks the paragraphs of the current XML document for well-formedness. In XML, a document is considered to be "well-formed" if it complies with the basic rules of the XML standard. Thus, the QM criterion checks, for example, whether every element has both an opening tag and a closing tag and whether the tags are nested correctly.
In this example, the closing tag of the <b> element has been forgotten in the target text paragraph what makes the paragraph not well-formed. Therefore, the QM criterion indicates a QM error:
In the following example, the order of the tag pairs was changed. This change, however, does not violate the well-formedness rules so that the paragraph is considered as well-formed. Therefore, the QM criterion indicates no QM error:
In the given example, the QM criterion Placeables order indicates a QM error because the order of the tags in the source and target languages is different.
In the following example, one of the two source paragraph tag pairs has been forgotten in the target paragraph. This change does not violate the well-formedness rules so that the paragraph is considered as well-formed either. Therefore, the QM criterion indicates no QM error:
In this example, the QM criterion Placeables usage indicates a QM error because the number of the tags in the source and target languages is different.
XLIFF element validation
Checks whether the XLIFF elements (inline elements and cloneable elements) are used correctly in the translation.
In the following example, the closing tag of the last cloneable element is missing in the target-language paragraph:
In the following example, the target-language paragraph does not contain the closing element ept of the element pair that the source-language paragraph contains: