### 1. Translation in practice - **Internationalization (i18n) vs Localization (l10n):** the difference between separating "making the software translatable" and "producing a locale-specific content". - **The role of each team:** the developers (extractable strings, placeholders, plural rules, file flow) and translators (meaning, tone, terminology, consistency) - **Example of Django's translation system**: template tags and filters, POT files, Django admin commands. ### 2. Common challenges in the real world - Not all translators have technical skills for working with translation files; Not all developers have translation skills to do it themselves - Working with multiple translators: causing overlapping edits, conflicting styles and review bottlenecks. - Synchronizing the work: between the various translators AND the developpers - Context and terminology - There are different translation file formats one can work with (XML, JSON, Properties, etc...) - Conclusion: There's a need for a unified tool that integrates the work of each team harmoniously ### 3. Enters Weblate - Lowering the technical bar for translators - Working with multiple translators: permissions, reviews, - Staying in sync by putting distributed VCS at the core of the system - Quality checks and consistency. - Adding context for translators for more accurate: screenshots, descriptions and glossary: - Formats and integrations — import/export, Django-friendly paths if applicable. ### 4. Adding AI in the loop - AI has revolutionized work in general and translations specifically - The limits of AI and how humans can (still) help - How Weblate's mode integrates Automatic translations in the workflow