Spanish Spoken Here
summary
Shows how to internationalize a Django site: mark translatable strings, run makemessages -l es and compilemessages, enable LocaleMiddleware and i18n_patterns for localized URLs, and use django-parler for per-language model fields. Demonstrates a tiny blog, explains language detection order (session, cookie, URL, Accept-Language), handling pluralization and msgctxt in .po files, recommends Weblate/Transifex or Poedit for translators, and cautions that migrating existing data needs per-model data migrations.
AI-written summary · about
chapters (14)
- 0:00Welcome
- 1:40Internationalization vs localization
- 3:07Django i18n setup
- 5:22Mark strings in models
- 7:31Generate .po files
- 9:44Translate .po files collaboratively
- 10:29Compile translations
- 11:14Translate HTML templates
- 14:09Pluralization and context
- 17:00Auto language detection
- 19:51Translate dynamic content
- 23:48Translate URLs for SEO
- 25:35Change UI language
- 27:01Summary
related talks
43mEita! Why Internationalization and Localization matter
29mEast Meets West When Translating Django Apps
19mData internationalization in Django
20mFinding translations, localisation and internationalisation
27mLocalize your WordPress projects
36mFrom Local to Global Service Based on Symfony2
08mLocalization for Real-World Use-Cases: Key Learnings from Onboarding Global Brands
56mDjangoCon 2008 Lightning Talks