Commit 4a99314b authored by Michal Čihař's avatar Michal Čihař

Recommend using ISO 639-1 language codes

Signed-off-by: default avatarMichal Čihař <michal@cihar.com>
parent 461ee95d
...@@ -98,10 +98,12 @@ Repository branch ...@@ -98,10 +98,12 @@ Repository branch
Which branch to checkout from the VCS and where to look for translations. Which branch to checkout from the VCS and where to look for translations.
File mask File mask
Mask of files to translate including path. It should include one * Mask of files to translate including path. It should include one *
replacing language code. In case your repository contains more than one replacing language code (Weblate can handle language names as well, but it
translation files (eg. more Gettext domains), you need to create separate is recommended to use ISO 639-1 language codes). In case your repository
component for each. For example ``po/*.po`` or contains more than one translation files (eg. more Gettext domains), you
``locale/*/LC_MESSAGES/django.po``. need to create separate component for each.
For example ``po/*.po`` or ``locale/*/LC_MESSAGES/django.po``.
Monolingual base language file Monolingual base language file
Base file containing strings definition for :ref:`monolingual`. Base file containing strings definition for :ref:`monolingual`.
Edit base file Edit base file
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment