Localization quality assurance is done in the following way:
Once a localized build has been compiled, the translator or native-speaking tester goes through the product
(plays the game, uses software, etc.) for the required amount of time and takes screenshots of problem areas
(things left untranslated or lines that are too long, improper coding, incorrect text orientation, contextual
In the developer's project management system (Jira, Trello, Asana), the tester creates a record of the
defects detected and makes the necessary changes to the string resources, either independently or with the
help of the developer.
The cost of localization testing is calculated according to the tester's hourly rate and the time required
Proofreading involves checking the text for errors in grammar, syntax and punctuation. To determine the
quality of a source text and the applicable proofreading rate, we perform a free initial assessment. Then,
proofreading is priced per 1,000 characters (including spaces).
Proofreading rates may vary by language. This is due to the language and the availability of a specialist
to proofread the text. Rarer languages have higher proofreading rates.