The QA Check for a transfer to the next workflow role can be configured in the workflow. Before the transfer to the next user, the so-called QA checks are used to check whether your processing violates defined rules. The user can eliminate these warnings and errors before the transfer.
QA checks are added to transfers using the workflow editor.
|Segments that exceed the maximum length||
All segments that exceed the maximum text length will be highlighted. To assign a segment a maximum text length, the segment in question must be assigned the attribute Size="X" in the XINI. In place of the X, enter the desired value for the maximum text length.
Note: If the "Size" attribute has been set, the value preset for the character count will be overwritten for this segment.
|Without translation||If the segment does not contain a translation in the target language and the empty entry (<e>) was not activated either, this QA Check highlights the corresponding segments.|
|Target language = Source language||Compares the segments of the target language with the source language segments. If they are equal, they will be highlighted.|
|Proposed changes not reviewed||The QA check proofs if change request were taken into account and highlights segments with non proofed change requests.|
The source language segment is searched for placeholders and compared with the segment of the target language. With this QA check ONTRAM detects whether the placeholders in the source language segment are also contained in the target language segments, and whether the placeholders appear in the same sequence.
Note: ONTRAM marks footnotes in MS Office documents with placeholders. If these placeholders are missing in the target language, the footnotes will be missing in the export as well.
|Structure errors||The target language segments are checked for structure errors. Structure errors are incorrect nested place holders.|
|Nested superscripts and subscripts||This feature checks for nested sub- and superscript formatting in the target language segments. This means that a single word has been marked as super- and subscript which may lead to faulty formatting.|
|Rejected author's corrections||
This QA Check checks whether author's corrections were adopted. Author's corrections that have not been adopted are highlighted by this QA check.
Note: If the Job Settings defined an AC adoption deadline and the QA Check for this Workflow step is set to mark this as an error, the Job cannot be transferred. For all other Workflow steps a warning is output upon transfer.
|Unrevised Fuzzy TM matches||
The QA check marks segments that are preallocated by Fuzzy-TM and have not been modified.
|Terminology not used||The QA check verifies whether terminology hits determined by the system for the source language have actually been transferred to the target language.|
|Segments with comments||The system determines all segments that contain segment comments and outputs them. This QA check should be defined as a warning.|
|Numbers and number format||
QA check for numbers: A new quality check "Numbers and Number Format" is now available. The QA check finds segments in which a number is missing from the target text or the number has the wrong decimal or thousand separators, depending on the target language. When the QA check is added to the workflow, the quality check is also available as a segment filter in the online editor.
Note: For Oracle, no numbers are found that are not surrounded by spaces.
|Text consistency: same translation for different source language||The system checks all target language segments and compares whether there are identical translations for different source language segments.|
|Text consistency: Different translation for same source language||The system checks all target language segments and compares whether there are different translations for identical source language segments.|