Translations are managed on Transifex. If you are interested in adding a new language, first let us know here. We will then set you up on Transifex. No coding skill are required for translations.

Policy for Translations

  • No Google/AI or other automated translations.
  • Only native or as-good-as-native speakers should translate.
  • As there is a need for continued maintenance, a translator should be also a user of vorta, having some own interest in the translation (one-time translations are not that helpful if there is no one updating them regularly)
  • A translation must have >90% translated strings. If a translation falls and stays below that for a longer time, it will not be used by vorta and ultimately, it will get removed from the repository also.

Adding a New Language

  • Only add a new language if you are willing to also update the translation in future, when new strings are added and existing strings change.
  • Request a new language by opening a new issue on Github. We will then add it on Transifex.

Updating a Language

  • Please only work on a translation if you are a native speaker or you have similar language skills.
  • Open a new issue on Github.
  • Edit the language on Transifex.

Using and Testing Transifex Translations

  • Extract from source files (needed after most code changes to update line number): make translations-from-source
  • Push to Transifex: make translations-push
  • Pull finished translations from Transifex: make translations-pull
  • Compile: make translations-to-qm
  • Test with specific translation: LANG=de vorta
  • Scale strings to test UI: LANG=de TRANS_SCALE=200 vorta --foreground

Style Guide/Glossary

We use Qt’s translation framework. Some guidelines for translations:

  • Original strings in .ui and .py must be American English (en_US) and ASCII.
  • Headings, buttons and dropdowns are titleized: “Apply Changes”
  • Field labels (same or next line) end with a colon and are titleized. “Allowed Networks:”
  • No full stop . at the end of short labels, but when it’s a full sentence.
  • If something is in progress, use three dots (no ellipsis): “Starting backup…”
  • Repo/repository = local or remote folder where Borg stores files.
  • Archive (not snapshot) = result of borg create execution, an identifier to find a collection of files in a repo, as they existed at a past point in time.

Not translated, always in English:

  • log messages (log file as well as log output on console or elsewhere)
  • other console output, print().
  • docs
  • py source code, comments, docstrings


  • GUI texts / messages

Add new strings for translation:

  • In Qt (sub)classes, use“English string”), scope will be the instance class name.
  • Elsewhere use vorta.i18n.translate("scopename", "English string")
  • To only mark a string, but not translate: vorta.i18n.trans_late (Translated string will be used later. E.g. when displaying settings.)

Required Software

To successfully run the translation-related Makefile targets, the translations maintainer needs:

  • make tool
  • pylupdate5 (from PyQt)
  • lrelease (from Qt package)
  • tx Transifex client (from Github, it will ask you for a API token when first running it)

Install on Debian:

$ apt install qttools5-dev-tools pyqt5-dev-tools

Install on macOS via Homebrew:

$ cd requirements.d && brew bundle