Skip to content

Ship Latvian (lv-LV): translation is now complete on Transifex #27394

Open

Description

@shpokas

Is your feature request related to a problem?

Latvian (lv-LV) is registered in locales.yaml but has ship: false, so it can't be selected in the UI and the backend strings aren't served. The inventory in #24563 lists lv_LV under "0% and no translators". That is no longer true: as of 2026-10-30 the Latvian translation on Transifex is complete.

  • frontend: 3409 / 3409 strings translated
  • backend: 1314 / 1314 strings translated

Describe the solution you'd like

Once the Transifex sync has brought the Latvian catalogs into the repository (web/xliff/lv-LV.xlf and locale/lv_LV/LC_MESSAGES/django.po, neither exists on main yet), set ship: true on the existing row and run make gen-locales, as described in the "Register a language" section of the translation docs:

- { tag: lv-LV, django: lv_LV, transifex: lv_LV, ship: true }

I'm happy to open that PR once the catalogs have landed, if that's easier for you.

Describe alternatives that you've considered

Running a locally patched build, which wouldn't help other Latvian users.

Additional context

I'm a native Latvian speaker and a translator on the Transifex lv_LV team. The translation was made with AI assistance and follows a shared glossary, with checks that every placeholder and markup tag matches the source. I personally reviewed the user-facing strings (login/enrollment/MFA/recovery flows, user settings, emails). The strings are still marked unreviewed on Transifex, pending the team coordinator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancement/confirmedEnhancements that will be implemented in the future

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions