The main aim of quality assurance (QA) checks is to help you efficiently handle different language-specific aspects in translations and make sure 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 Proofreading mode in the Editor. QA checks would help you 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.
To enable QA checks in your project, follow these steps:
Empty translation — strings that lack translation.
Length issues — translated strings that are longer than the limit of characters you set.
Tags mismatch — strings that use HTML 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 difference 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 current translation is wrong tag.
Consistent terminology — checks whether the source words are translated accordingly to the respective glossary terms.
Spelling — words that aren’t present in the dictionaries Crowdin supports.
ICU syntax — the correct usage of ICU message syntax in translations.
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.
If QA check status is Issues Found you can click on it, then on View Issues to get detailed information on the found issues.
In the unfolded language details section you will see the number of the found issues. To see them in detail click Suggestions with QA issues.
After it, you will be redirected to the Proofreading 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.