# Proofreaders' QA Checker: Ensuring Quality Translations

## 🧰 What's a QA Checker? <a href="#the-qa-checker-is-here" id="the-qa-checker-is-here"></a>

The quality assurance checker – *or **QA checker**, for short* – is a tool used by project managers to ensure quality translations. It checks for formal errors that may have been missed by translators (such as double spaces or missing characters).

## 👥 Who can use the QA checker?

The QA checker is only accessible to **proofreaders** and **project managers**.&#x20;

## **🔧 What does it do?**

Specific translation elements will be checked to make sure that translations are consistent and that they don’t cause any unwanted bugs. After running the checker, proofreaders will have to edit target translations to fix QA issues and approve them again manually.

*Note that QA checker settings can only be edited by project managers or owner.*

**The QA checker currently checks for:**

<table><thead><tr><th width="247">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Empty translations</strong></td><td>If the source string contains data but your translation doesn’t, an <em><mark style="background-color:red;">error message</mark></em> will be displayed.</td></tr><tr><td><strong>Tag mismatch</strong></td><td>If tags (as well as ID attributes and CDATA tags) are inconsistent between the source and the translation, you will receive an <em><mark style="background-color:red;">error message</mark></em>. This is useful for strings that may contain tags used in code.</td></tr><tr><td><strong>Spaces mismatch</strong></td><td>If there are any missing spaces or too many spaces in a row, an <em><mark style="background-color:red;">error message</mark></em> will be displayed.</td></tr><tr><td><strong>Variable mismatch</strong></td><td>If the source string contains variables, they must be copied and pasted as such, and not translated. If the variables differ from the source string, a <em><mark style="background-color:orange;">warning message</mark></em> will be displayed.</td></tr><tr><td><strong>”Incorrect translation” issues</strong></td><td>If an issue is open indicating that the “current translation is wrong”, a <em><mark style="background-color:orange;">warning message</mark></em> will be displayed.</td></tr><tr><td><strong>ICU syntax</strong></td><td>If the ICU message syntax isn’t correct, an <em><mark style="background-color:red;">error message</mark></em> will be displayed.</td></tr><tr><td><strong>Duplicate translation</strong></td><td>If the translation already exists, an <em><mark style="background-color:red;">error message</mark></em> will be displayed.</td></tr></tbody></table>

### QA error types:

There are two types of QA errors:

<mark style="background-color:red;">Error messages</mark>, which will prevent translation approvals until flagged errors are removed or edited.

<mark style="background-color:orange;">Warning messages</mark>, which will not prevent translation approvals.

***Note:** removed the **special character mismatch** setting due to false positive errors on bracket usage.*

## 🧐 How do I open the QA checker?

To open the QA checker, you can use **proofreading mode** or the **translation editor:**

### 1. Using proofreading mode to open the QA checker:

To open the proofreading mode, click on the language you wish to check and press the **"Proofread"** button in the dropdown menu.edit

<figure><img src="https://4251351290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ4zSrJvXs9WU5ydWYb7d%2Fuploads%2Fzhynm6Fp7jmNUegMoPgq%2Fimage%20(12).png?alt=media&#x26;token=49d8f44c-0915-45e1-8078-94af98ff2ffc" alt=""><figcaption></figcaption></figure>

Once proofreading mode is enabled,  display strings that have been flagged by the QA checker using the **"QA issues"** > **"All"** filter, on the top left part of the editor.

<figure><img src="https://4251351290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ4zSrJvXs9WU5ydWYb7d%2Fuploads%2Fj3UcU4G7SX0QjD6utqMY%2Fimage.png?alt=media&#x26;token=92e269f3-48f6-486e-b556-191dab5a69f7" alt=""><figcaption></figcaption></figure>

Translation errors will now be displayed in red text under flagged strings. An explanation on how to fix these errors will also be provided.&#x20;

To resolve these issues, simply edit translations according to the QA check report and approve the translation.

### 2. Using the translation editor to open the QA checker:

By enabling the **"QA issues"** > **"All"** filter (on the top left part of the editor), you can display QA issues directly onto the translation editor – right under the translation field, preexisting translations, and MT results.

To resolve these issues, simply edit translations according to the QA check report and approve the translation.

<figure><img src="https://4251351290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ4zSrJvXs9WU5ydWYb7d%2Fuploads%2FrZy9KwopQZfM144Lxg1t%2Fimage.png?alt=media&#x26;token=4114c984-a12c-4975-979a-5c52038ac6d0" alt=""><figcaption></figcaption></figure>

Now, you're all set to resolve QA issues!

If you wish to know more about the QA checker, you can check out [Crowdin's documentation on Quality Assurance checks](https://support.crowdin.com/qa-checks/).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.prestashop-project.org/translating-prestashop/translating-prestashop-software-basics/translating-on-crowdin/proofreaders-qa-checker-ensuring-quality-translations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.