goauthentik / goauthentik/authentik

Translation tracking issue

Open
#24,563 1 comment 0 reactions 2 assignees Claimed by @GirlBossRush View on GitHub
area:backend area:docs area:frontend enhancement enhancement/confirmed i18n
Dominant language
Python
Stars
25.6k
Forks
2k
Avg merge
1d 1h
Merged PRs (30d)
644

Description

This issue is for tracking improvements we'd like to make to our translations.

Here's a somewhat sorted list of things we want to do:

- [ ] fix the duplicate files in web/xliff
- [ ] decide on whether to keep `_` or `-` in the language tags
- Django wants `_`
- web wants `-`
- transifex?
- [ ] separate translations in the frontend between the different interfaces (flow/user/admin), to allow translators to prioritise user-facing translations
- [ ] evaluate all the translation strings we have in the backend and remove translations on the strings that are not shown in the UI (for instance, all the help_text, the verbose_name, etc.)
- [ ] ensure translation fallback is happening between languages with the same language code but different region code (for instance between `pt_PT` and `pt_BR`)
- [ ] define a clear policy (in `website/docs/developer-docs/translation.md`) about which languages we allow
- for instance, we already have `fr_FR` so we won't allow `fr_CH` or `fr_BE` since they're so similar, it would just add translation burden on our translators
- [ ] cleanup transifex teams

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.