Translating Keycloak is a collaborative effort

Keycloak runs in a lot of regions and countries, and translations help Keycloak to reach a wider audience by making the platform usable for speakers of various languages.

For translations, Keycloak now integrates with Weblate to simplify the process. This session will look into how the process works, how you can join the process and will answer the questions from the community.

Transcript

1. Translating Keycloak is a collaborative effort Alexander Schwartz | Principal Software Engineer | Red Hat Keycloak Hour of Code | April 2025
2. Translating Keycloak is a collaborative effort ⭐ Make translations shine for users 🏆 Make life simpler for translators 📜 Less day-to-day work for maintainers 🌡 Know the status of our translations
3. Translated components
4. Translated languages
5. Why using Weblate 1. Translators don’t need to know about GitHub and pull requests 2. Notifications for new and changed source strings 3. Statistics on missing strings
6. Translation Process Community: 1. Register for Weblate, and accept contributing guidelines 2. Translating via Weblate Keycloak maintainer: 1. Check CI status, check translation via Google Translate, merge Language maintainer: 1. Review translations, mark them “approved” https://github.com/keycloak/keycloak/blob/main/docs/translation.md
7. Supporting actions 1. Automated checks to avoid common formatting mistakes (misc/theme-verifier) 2. Gradually improving documentation 3. Reminders to language maintainers when a release is close 4. Simplifying RTL email templates 5. …
8. Translating Keycloak is a collaborative effort ⭐ Make translations shine for users 🏆 Make life simpler for translators 📜 Less day-to-day work for maintainers 🌡 Know the status of our translations
9. Contact Alexander Schwartz Principal Software Engineer aschwart@redhat.com https://www.ahus1.de @ahus1.de @ahus1@fosstodon.org