Project Management

Quality Assurance

Quality Assurance (QA) is a feature built into both Memsource Editors. It detects errors in translation by comparing source and target segments, checking the term base, spelling, content of the tags, etc.  Linguists should run the QA check before they set the job to Completed and they should resolve all the QA issues. Keep in mind that Quality Assurance software is not intended to replace human reviewers—it simply helps translators detect formal errors and improve the overall translation quality.

There are two ways in which Memsource helps with QA:

  1. Instant QA is run on a segment when it is confirmed. If there are some issues, the segment is not saved to a translation memory. The Linguist must resolve the QA issues in order to confirm the segment.
  2. Manual QA checks for all segments in the job—usually this is run by the Linguist before the job is set to Completed.

Quality Assurance Setup

General settings can be accessed from the Setup page under Project Settings, by clicking on Quality Assurance. All selected checks will become the default QA settings for all projects. If needed, these settings can be adjusted later on at a project level by going to the project, clicking on Edit, then expanding the Quality Assurance section.  in a similar fashion can be Quality Assurance setting edited in a project template.

By default, all QA warnings can be set to "ignore" by Linguists/Vendors. However, for some QA checks, the Project Managers can disable the "Can be ignored" option in the QA settings. Linguists and Vendors will not be able to ignore these warnings.

QA settings

List of QA Checks

The QA checks cover errors that range from spelling errors to tag issues. They even check for inconsistent terminology. Below, you'll find a list of the issues that the QA checks cover.

QA check Note Instant QA
Empty target The target contains no characters or tags. Yes
Trailing punctuation Trailing punctuation is different in the source and target.
For example, the source ends with "." but the target does not or vice-versa.
Inconsistent translations
  • A segment with an identical source but a different target precedes the checked segment.
  • A segment with an identical target but a different source precedes the checked segment.
  • Repetition exceptions and segments with an empty target are skipped.
Newer version in a preceding workflow step available Checks whether newer versions of segments exist in preceding Workflow steps.
For example, a translator has modified a segment in the Translation Workflow step after it was revised in the Revision Workflow step.
Missing numbers The number in the source is not present in the target.
For example, the source has the phrase "1 and 2", but the target reads "1 and 3".
Repeated words Two or more adjacent words in the target are identical. Yes
Multiple spaces There are multiple spaces in the target but not in the source. Yes
Leading and trailing spaces There is a leading or trailing space in the target but not in the source. Yes
Tags & formatting Tags/formatting are missing or invalid, or there are missing or redundant line breaks.
Example: the source contains "{1} {2}" but the target reads "{1}".
Inconsistent tag content The tag content between the source and its corresponding target tag differ.
For example, the source shows "<a href="">" but the target contains "<a href="http://">".
Empty tag content The target tag content is empty, while the source tag content is not.
For example, the source reads "<a href="">" but the target shows "".
Tags-joined segments The number of {j} tags is different in the source and target.
For example, the source is "xxx{j}yyy" but the target is "xxx yyy".
No text between the tags There is a paired tag with no text between the tags in the target but not in the source.
For example, there is {1>abc<1} in the source and {1><1} in the target.
Nested tags Paired tags in the target are misplaced.
For example, there is {1>{2>abc<2}{3>abc<3}{4><4}<1} in the source and {1>{2>abc<2}{3>abc{4><3}<4}<1} in the target.
This option is disabled by default, but it is important to enable it for projects with Excel files.
XLIFF tags Paired tags (such as bpt and ept) are in the incorrect order in the completed target file.
For example, the source contains "bpt bpt ept ept" and the target contains "bpt ept ept bpt".
  • The terms (with status Approved) in the source do not have a corresponding term translation (status New or Approved) in the target.
  • A forbidden term is used for the translation. (Forbidden terms in the source are ignored.)
Note that only terms within the source will be checked.
Forbidden terms without a source

This is based only on target terms with no source term.


Spelling The target contains misspelled words. Yes
Not confirmed segments Checks to make sure each segment is confirmed. No
Unresolved conversation Ensures that no segment contains an unresolved comment in a conversation. No
Maximum target segment length in characters The target segment length is greater than the given parameter (default 100000). Yes
Maximum target segment length in % of source The target segment length is greater than the given parameter (default 130%). Yes
Not allowed The target contains strings that are not allowed.
Characters, or alternatively, utf-8 codes, can be entered as strings that are not allowed. Numerous strings can be entered this way, separated by commas.
Target text identical with source one
  • This is a QA check for text copied from the source to the target.
  • No warning will be displayed for segments containing only plain numbers, tags, or non-translatable characters.
  • Segments translated using the Memsource Non-translatables feature are ignored in this QA check.
Unedited TM fuzzy match

A fuzzy TM match has been confirmed without being edited.


Unedited NT/MT fuzzy match

A fuzzy NT/MT match has been confirmed without being edited.


Extra numbers in target The target contains an extra number that the source does not. Yes
  • This section can be used to define checks based on Regular Expressions as well as Descriptions that will be displayed in the Editors when such an issue is identified.
  • Multiple conditions can be set using the PLUS button.
  • Memsource checks whether the counts of the regexp matches differ between the source and the target text.

Running a QA

For more details about running the QA in the Editors, please refer to our Quality Assurance Pane article.

QA Status for Jobs

Whenever a QA check is launched for a job, the outcome is saved with the translation job. If you hover over the job's confirmed percentage, an information box will appear that includes the QA status related to the job. These include the following:

  • QA Warnings: Not launched - The QA has not been launched for this job.
  • QA Warnings: Incomplete - The QA has been launched only for part of a job (e.g. the user did not click the "Show more" link at the bottom of the QA warnings list). Or, the QA has been launched for the entire job but the job was later edited.
  • QA Warnings: 2 (1 ignored) - The QA has been launched and it includes a total of 2 warnings of which 1 was marked as ignored.

Forcing Providers to Run a QA Check

It is possible to prevent your Providers (Linguists and Vendors) from being able to set the job to Completed unless they run the QA check and deal with all its warnings. Project Managers can also select which QA checks can be set to "ignore" by your Linguists.

  1. Open your project and click the Edit button in the top right corner.
  2. Expand the Quality Assurance section and check Linguists may not set jobs with QA warnings to Completed at the bottom of the list.
  3. Uncheck the Can be ignored box for any QA checks you want to prevent the Linguist/Vendors from ignoring.

Instant QA settings

If you would like to force Linguists to use Instant QA—to check every segment before they save it to the TM—go to Project, Edit, and Access and Security and unselect Users may turn on/turn off Instant QA in editors. This will set the Editor's option Instant QA to ON and the Linguists will not be able to disable it. This feature is useful when you have several Linguists working on the same TM and the same target language. The segments with QA issues will not be saved to the TM and therefore won't be offered to other Linguists as a valuable TM match.

Issues Which Can be Solved by Running a Proper QA

Export Failed, File Could not be Generated
There are missing or misplaced tags in your file. Run the quality assurance with the following options selected in your project:

  • Tags/Formatting
  • Joined Tags
  • Empty Pair Tags

Correct the problems identified by the quality assurance check and re-export the file.

Unresolved QA Warnings
Project owners can prevent Linguists and Vendors from setting jobs with QA warnings to completed. As a Linguist or Vendor, you will see this error message when you try to set a job to Completed without running a QA check or when leaving some warnings unresolved. To resolve this, please proceed like this:

  1. In the Memsource Editor, click on the QA Pane, located in the bottom right.
  2. Click on the Run button at the top.
  3. Resolve all QA warnings that get displayed. If you get a false warning, you can also ignore the warning by clicking on the "i" column. Once the warning has been ignored, it will turn grey.

Translation and Terminology Inconsistencies
The Inconsistent Translations check can detect the following inconsistencies:

  • A segment with an identical source but a different target precedes the checked segment.
  • A segment with an identical target but a different source precedes the checked segment.

There is a feature in the TB section where you can choose whether or not you want to have a certain term base included in the QA check.

The Terminology check can detect these inconsistencies:

  • The terms in the source do not have a corresponding term translation in the target.
  • A forbidden term is used for the translation (Forbidden terms in the source are ignored).
Was this article helpful?



Please sign in to leave a comment.