Quality Assurance Checks

The main aim of quality assurance (QA) checks is to help you efficiently handle different language-specific aspects in translations and ensure they are formatted the same way as the source strings and will fit the UI just as well. Some typical QA check issues include missed commas, extra spaces, or typos.

With QA checks, a proofreader will see all those kinds of issues that should be fixed, as they will be highlighted in the Side-by-Side mode in the Editor. QA checks help to detect some common mistakes easily and quickly. It’s recommended to review and resolve all QA check issues before building your project and downloading translations.

Configure QA Checks

By default, QA checks are enabled. To select the needed QA checks in your project, follow these steps:

  1. Open your project and go to Settings > QA Checks.
  2. Ensure that Enable QA Checks is selected.
    QA Settings
  3. Select the QA check types according to your preferences.
  4. Scroll down to the bottom of the QA Checks list and click Save.
    QA Checks Save Settings

QA Check Parameters

Empty translation – strings that lack translation.

Length issues – translated strings that are longer than the limit of characters you set.

Note: To set character limits for specific strings, go to Sources > Strings. Click Edit on the needed string and set the max. length. This means that translators will be notified that a translation for the particular string can't be longer than the specified limit. This is useful when the space for the given text is limited.

Tags mismatch – strings containing HTML tags might lack some opening or closing tags in translations.

Spaces mismatch – multiple spaces in a row, missing spaces.

Variables mismatch – placeholders that lack some parts of code or have the odd ones.

Punctuation mismatch – punctuation mistakes or differences in the punctuation marks.

Character case mismatch – lower or upper case used differently in source and translated strings.

Special characters mismatch – new paragraphs, currency signs, and other special characters used differently in source and translated strings.

“Incorrect translation” issues – created issues with the “current translation is wrong” tag.

Spelling – words that aren’t present in the dictionaries Crowdin supports.

ICU syntax – the correct usage of ICU message syntax in translations.

Consistent terminology – checks whether the source words are translated accordingly to the respective glossary terms.

Note: Currently available for English, German, Spanish, French, Italian, Dutch, Norwegian, Polish, Russian, Swedish, Ukrainian, Japanese, Korean, Chinese Simplified, and Turkish.

Duplicate translation – translations that duplicate already existing translation.

FTL syntax – the correct usage of the FTL syntax in translations.

Android syntax – the correct usage of the Android syntax in translations.

QA Status Options

OFF – when it’s not enabled.

IN PROGRESS – while it’s working.

NO ISSUES – when it found no mistakes.

ISSUES FOUND – when it found some mistakes.

More Information On Found Issues

If the QA check status is Issues Found, you can click on it, then click View Issues to get detailed information on the found issues.

QA checks view

In the unfolded language details section, you will see the number of issues found. To see them in detail, click Suggestions with QA issues.

QA checks details

After it, you will be redirected to the Side-by-Side mode of the Editor to check the list of strings with QA issues. You can approve the existing translations if they are supposed to be the way they are or make changes and then approve the translations.


Once enabled, QA checks will work in the background and scan the translations for potential QA issues.

Was this article helpful?