It is a set of mechanical checks that pick up errors in translated files that a human eye easily misses. These may be missing translations, number errors, inconsistencies, punctuation issues etc. Many QC tools also contain a glossary consistency checking function, which checks whether the terms appearing in the glossary or termbase have been used in the translation.
Because no matter how conscientious and good a translator or a reviser is, certain issues are easily missed, especially in a longer translation. A QC check helps to ensure that there are no errors that a mechanical QC check could have picked up. It should be carried out at the end of each translation assignment together with complete spellchecking of the translation.
QC checking is a mandatory step in STP workflows, and you are asked to confirm that QC checking has been done when you complete a project and return the STP QC checklist. All projects and files that can be QC checked, either using a built-in QC checking function in the translation tool or using an external QC checker, must be QC checked. A QC checker is only able to check bilingual files, that is, files inside a translation tool or files exported in bilingual format (source and target present) from a translation tool.
Most sophisticated translation tools such as memoQ and SDL Trados Studio have a built-in QC checker which can be run on a single file at a time, or in batch mode on all files in the project (recommended). Refer to instructions provided to you by STP or the tool’s internal Help for more information about how to run the QC check.
External QC tools may also be used as long as they support the bilingual file type in question. There are many external QC tools on the market. At STP, we use ApSic Xbench and Yamagata QA Distiller.
These checks should be included as a minimum level of checking:
100% matches and 101% matches (Context/Perfect/ICE matches) can be excluded from the QC check in most tools if these don’t belong to the scope of the project.