The custom quality assurance (QA) checks help efficiently handle language-specific aspects such as punctuation, numbers, and regular expressions to ensure more accurate QA check results and high-quality translation in all languages.
With custom QA checks you can detect the exact mistakes you need. It helps customers to avoid the mistakes in the suggestions and to translate the content more proficiently.
To make the QA check work you need to provide the Javascript-based code snippet.
Every code snippet includes a crowdin
object and the number of following properties:
object crowdin {
string sourceLanguage,
string targetLanguage,
object context {
?int maxLength,
?string pluralForm
},
string contentType,
string source,
string translation
}
Every code snippet should return the response whether the custom QA checks have passed successfully or failed.
We recommend using Custom Script Editor as the tool for the development and debugging for Crowdin custom QA checks.
Crowdin code snippet has the following limitations:
- The code is completely sandboxed. Neither the browser context nor NodeJS context is available
- Standard objects like
date
,math
and similar ones aren't available - Crowdin limits the time of running the custom QA check: the user’s code can run up to 100 ms. If the code snippet is too complex or has any mistakes, the custom QA check can be processed longer and will be stopped. In this case, the issues should be corrected. Then QA check should be run again.
To learn more details about creating your own custom QA checks, please read Code Snippet for Custom QA Checks article.
- Generic
- Localization
- Numbers
- Punctuation
- Symbols
- Words
If you want to contribute please read the Contributing guidelines.
Custom Quality Assurance Checks are licensed under the MIT License. See the LICENSE file distributed with this work for additional information regarding copyright ownership.