Context: Missing ingredient in multilingual software translation
summary
Claim: showing text keys in the running app plus matched screenshots with the normal content exposes reused keys, concatenated fragments, hard coded strings and layout fit problems so translators give correct translations on the first iteration. Implementation removes or empties resource values or uses a fallback locale, show text keys in UI, then rerun Selenium to capture matched screenshots to pair key and content images. Works on pages with few keys like a three field form, reduces rework, and requires tests that avoid locators based on text and use nonblocking verifications.
AI-written summary · about
chapters (9)
- 0:00The challenges of translation
- 3:24The software translation flow
- 5:54Contextual limitations
- 9:00Using Selenium for context
- 11:51Common translation pitfalls
- 14:12The missing ingredient
- 18:24Implementation strategy
- 20:45Best practices for testing
- 23:28Conclusion and workflow
related talks
40mLinguistic and Esthetic Testing of Kaspersky Lab Software
53mInternationalization - Translating Applications in Qt
20mFinding translations, localisation and internationalisation
48mContinuous Localization in Enterprise Web Projects
26mWhen localisation & design talk to each other
26mContinuous Localization in Enterprise Web Projects
16mKeynote
31mInternationalizing your App