Beyond Po: How to Make Django Work...
summary
Concrete rules and tools: use Django i18n_patterns and get_language_bidi to branch templates, keep canonical URLs in Latin and serve localized slugs as front‑end mappings, avoid per‑language sites unless you accept extra management commands, prefer same-table translations to avoid expensive joins, expect Python 2 Unicode errors and migrate to Python 3, use CKEditor with RTL support and a Jalali date widget that converts on save, use SASS mixins to compile RTL/LTR variants which the talk claims can cut work by 50% development time.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:41Planning your architecture
- 4:34URL and site strategies
- 7:59Translation techniques
- 11:20Django settings and code
- 13:40Handling RTL layouts
- 15:29Encoding and Python tips
- 17:58Calendar systems
- 19:18Internationalization patterns
- 20:23Frontend and styling tips
- 23:42Q&A and final thoughts
related talks
25mBecoming a Multilingual SuperHero in Django
19mData internationalization in Django
01h 06mEffective Django
53mDjango productivity tips and tricks
53mDjango productivity tips and tricks
01h 39mTUTORIAL: Parlez-vous Wagtail? Internalization for Python/Django developers
23mLessons Learned in a Large Django Project
21mBuilding maintainable Django projects: the difficult teenage years