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, issues that should be fixed will be highlighted on the Proofread workflow step. 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 > Quality assurance.
2. Select the QA check types according to your preferences.

3. For each selected QA check type, select whether it should be possible to save translations with QA issues using two available options: Error and Warning.

   Warning – the system notifies translators about the QA issues with suggestions on how to fix them, but it would still be possible to save the translation using the Save anyway button.
   Error – the system notifies translators about the QA issues with suggestions on how to fix them. It wouldn’t be possible to save the translation until all QA issues are fixed.

Spell Checker Ignore List

If your project contains some uncommon words that are not recognized by the Spell checker, you can add them to the Ignore list to exclude them from being checked.

To review the words added to the Ignore list for the Spell checker, follow these steps:

1. Open your project and go to Settings > Quality assurance.
2. Click Ignore list on the top right side.

QA Check Parameters

Omissions
Strings that lack or have excessive translations.

• Source is empty but the translation is not

• Translation is empty but the source is not

Translation length limit
Translations that are longer than the limit of characters you set.

Tags
Strings that use HTML might lack some opening or closing tags in translations.

• Inconsistent tags in the source and translation

• ID attributes consistency

• CDATA tag consistency

Spacing
Multiple spaces in a row, missing spaces.

• Spaces around special symbols

• Start and end newline characters

• Start and end spaces

• Multiple spaces in succession

• Non-breaking spaces

Variables
Placeholders used in a translation match placeholders used in the source string.

• Common variables

• Python, Java, .NET, C/C++, Ruby on Rails, Twig, PHP, Freemaker variable placeholders

• Custom variables (per request)

Punctuation
Punctuation mistakes or differences in the punctuation marks.

• Inconsistent punctuation in source and translation

• Spacing before and after punctuation marks

Character case
The lower or upper case that used differently in source and translated strings.

• Initial capitalization

• Unexpected multiple capitalized characters in succession

Special characters
New paragraphs, currency signs, and other special characters that used differently in translated strings.

• Bracket consistency

• Markup language entities

• Quotes and quote escapes

Open translation issues by project members
Show reported translation issues on the Proofread workflow step.

Spell checker
Underline misspelled words.

ICU Markup syntax check
The correct usage of the ICU message syntax in translations.

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

Duplicate
Translations that duplicate already existing translation.

FTL Markup syntax check
The correct usage of the FTL syntax in translations.

Android Markup syntax check
The correct usage of the Android syntax in translations.

See Also

• Custom Quality Assurance Checks