About the service
I do localization QA on a live, working product, not on a spreadsheet of strings. Translation that looks perfect in isolation easily breaks the moment it lands in a real button, table cell, push notification or legal footnote. That's where I work: I open every localized screen, walk through real user scenarios and check that every string fits in its container, preserves variables and placeholders, reads naturally and matches the tone your brand uses in that market.
My focus is specifically contextual linguistic quality in software, and that's not the same as what a translator, editor or QA engineer does. A translator delivers correct phrases, a QA engineer confirms the code works, and I sit between them and verify that correct phrases behave correctly inside the interface. I catch cut-off labels, text overlap, strings attached to the wrong element, untranslated leftovers, language mixing on one screen, broken plural forms, shifted or cut-off numbers, dates and currencies, and wording that's grammatically correct but contextually or culturally off.
You get a clear report with priorities: reproduction steps, screenshots, affected language and screen, exact string key if available, and specific fix suggestions for each issue. I'm ready to test iteratively build-to-build, double-check after fixes and work to your glossary and style guide so the entire product feels written by native speakers, not assembled from translation memories.
— Contextual review of localized interface, emails, notifications and stores
— Checking for cut-off, overflow, line breaks and layout-text conflicts
— Finding wrong strings, missed translations and language mixing
— Validating plural forms, gender, dates, numbers, currencies and formats
— Tone, register and terminology consistency against your style guide
— Prioritized bug reports with steps, screenshots and fixes
My focus is specifically contextual linguistic quality in software, and that's not the same as what a translator, editor or QA engineer does. A translator delivers correct phrases, a QA engineer confirms the code works, and I sit between them and verify that correct phrases behave correctly inside the interface. I catch cut-off labels, text overlap, strings attached to the wrong element, untranslated leftovers, language mixing on one screen, broken plural forms, shifted or cut-off numbers, dates and currencies, and wording that's grammatically correct but contextually or culturally off.
You get a clear report with priorities: reproduction steps, screenshots, affected language and screen, exact string key if available, and specific fix suggestions for each issue. I'm ready to test iteratively build-to-build, double-check after fixes and work to your glossary and style guide so the entire product feels written by native speakers, not assembled from translation memories.
— Contextual review of localized interface, emails, notifications and stores
— Checking for cut-off, overflow, line breaks and layout-text conflicts
— Finding wrong strings, missed translations and language mixing
— Validating plural forms, gender, dates, numbers, currencies and formats
— Tone, register and terminology consistency against your style guide
— Prioritized bug reports with steps, screenshots and fixes
