Continuous Localization in Enterprise Web Projects
summary
Says 50% of users skip English and a survey finds ~67% of teams use no tooling, so the talk claims continuous localization prevents localization from becoming a release blocker. Describes moving from brittle app-specific scripts to a cloud TMS with scan and build commands wired into a Jenkins plugin, publishing translation files to CDN, using translation memory, machine translation, screenshot context and a fake language for automated checks, and extracting i18n into a decomposed service that delivers instant updates across many apps.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:34Waterfall Localization
- 6:26Agile Localization
- 7:24Continuous Localization
- 9:04DO we need to complicate?
- 9:33MACHINE TRANSLATION
- 9:58Powerful API for automations
- 16:25Fake Language
- 16:55Translations Coverage Validation
- 17:39Screenshot Support
related talks
48mContinuous Localization in Enterprise Web Projects
21mContinuous Translation: I18n in Agile Projects
23mAutomating Localization
23mDriving Seamless Localization
01h 11mSpeak My Language %app%
30mInfluence your customer outreach with best practices for internationalization
39mThink globally, act locally with i18n on the web
21mInternationalisation, Content, & Diversity: Reaching New Markets Through Technology