Home   ·   Index   ·   Search

memoQ 2015: QA

Processing QA

QA (Quality Assurance)  is an automated process where a translation is checked based on a number of parameters to spot potential errors.
QA can never replace human revision, but it is a helpful tool for translators to spot easily overlooked errors , much like you would use spellchecking.

Linguists are required to run QA in memoQ before delivery of any project.

QA settings

STP server projects are set up with our default QA settings in most cases. You can check this on the Settings pane of the project overview, under QA settings. There may be projects where custom QA settings are used and in those cases they will be named differently.

QA checking

QA checking uses settings predefined for the project as selected by the PM. QA checking checks for issues such as inconsistently translated segments, double spacing and punctuation, duplicate words in the target. 

Run the QA with Run QA and the below dialog window will open.

Here you can define the scope of the QA check. Please make sure you are including the entire project and include/exclude locked segments according to the scope assigned to you. Clicking OK will apply the project's QA settings on each segment of the selected scope. Normally you will want to tick the Proceed to resolve warnings after QA box, which will prompt memoQ to open a separate tab where you can process the QA results after running the QA check. You can also resolve errors and warnings separately, based on the QA check, but you should always use Run QA if any edits have taken place since you last did so.

If you wish to display a separate view with inconsistently translated segments, tick Create view of inconsistent translations (see above picture) in the Run QA dialog. The inconsistencies can be viewed in the Views tab separately from the rest of the QA check.

Resolving errors and warnings

Once Resolving errors and warnings tab opens, process the segments at the top of the QA window or return back to the translation view by double-clicking the error line to see the segment in context in the translated file. The QA checking view is interactive, so as soon as you fix and confirm a segment, the corresponding QA error line turns green. Remember to confirm all changed segments. You can also ignore issues individually or by type, and hide all ignored errors if you wish.

You can export the QA checking report to HTML if you wish.

See more information about QA checking in the memoQ 2015 Help: http://kilgray.com/memoq/2015/help-en/resolve_errors_and_warnings_tab.html

Terminology consistency checking

If defined, QA checking also checks for consistency with termbases, see more information about optimising termbase content in Match settings and case sensitivity

If termbase consistency checking is activated, memoQ reports terms translated inconsistently with the termbase. Iissues are listed in the QA checking view with the message "Translation of source term "xxx" is missing from the target". However, the actual translation of that term from the glossary is not displayed, so you can't be sure whether the term is reported because the translation is truly incorrect, or just a conjugated form or appears in a compound noun. In order to make sure the correct term is used, you have to return to the translator editor view for that segment by double-clicking on the error and check the glossary entry from the Translation results pane.


memoQ checks tags during QA. Files can't be delivered if there are unresolved (critical) tag errors or errors indicating that "XML is not well formed", so please check these thoroughly!