Skip to content

i18n templates for more languages

For really using the impact / potential of hosted.weblate.org, I recommend shipping as many translation files, as possible (not sure, if I got them all).

My recommended workflow for hosted.weblate.org is: push on commit (i.e. after an author updated a translation, some hours later, the update gets pushed upstream) and mirror upstream pushes to weblate when they appear here in this repo. These two workflow steps avoid merge conflicts in 18n files.

Esp. make sure that update-po.sh only gets used when all changes on hosted.weblate.org have successfully been pushed upstream.

Merge request reports