Building your translation process
summary
The Symfony Translator component is simple and reliable but real problems appear at four or more languages, especially with merge conflicts when files live in git; static files with 8 languages and 100 new keys break teams. Recommended process stores the true source in the cloud (example Loco), downloads XLIFF at deploy, and uses an extractor, a translation logger that records which keys are used, a simple language switcher and RTL CSS tweaks. A hard rule applied here is never change translations; for urgent fixes use fallback or machine translate.
AI-written summary · about
chapters (18)
- 0:00Start
- 2:47Open source
- 5:33Translator
- 6:17Loaders / Dumpers
- 9:27Your translation source
- 12:37Download at each deployment
- 12:55Translation file format
- 13:36Use a converter
- 18:36Language switcher
- 22:20Adding new translation
- 22:53Extract from source
- 24:42Feature branches
- 26:07Change translations
- 26:57Deploy new translations
- 33:41Direction
- 34:17Swedish
- 37:02TOOLS ARE GREAT
- 38:55SILVER SPONSOR
related talks
38mTranslating a Symfony Application Effectively
38mDrupal 8's Multilingual APIs
02h 37mSymfony 4 best practices (Part 2)
57mEating spaghetti with Symfony
44m"Language Overlay - How it works"
50mSymfony Messenger: the sharpest tool in your PHP toolbox
36mFrom Local to Global Service Based on Symfony2
45mMessy data != Messy code