For a list of translators, see TRANSLATORS.md
If your name is missing, please contact us.
Translations are handled on the Launchpad translations page.
To get started:
Once your translations have been approved, they will be merged into Nicotine+’s GitHub repository, at the very latest before a new Nicotine+ release.
As strings change in the Nicotine+ source code, the translation template file should also be updated regularly.
To update the template (.pot) file:
po folder by running
intltool-update -p -g nicotine
Translations should be imported to the GitHub repository regularly, at the very latest before a new Nicotine+ release is tagged.
To do this:
Export all translations in PO format
Add the updated files to the
Commit the files
Also remember to add new translators to the list of translators, located in TRANSLATORS.md and
Nicotine+ will try to autodetect your language based on what locale you’re using.
For testing purposes Nicotine+ can be forced to use a specific language. You can do it by setting your locale before starting Nicotine+ ex:
* English: `LC_ALL=en_US.UTF-8 python nicotine` * French: `LC_ALL=fr_FR.UTF-8 python nicotine` * ...
Nicotine+ will first try to find your translation files in your project folder. It’s particularly useful for testing translations from the git source tree or if your are using Python virtualenv framework.
To use translations when running Nicotine+ from your project folder, you need to generate .mo files by running
python3 setup.py build. The files will be located in the
If Nicotine+ doesn’t find the .mo files in your project folder, it will fall back to searching in your system locale path which is OS specific. A GNU/Linux distribution package will put them in the system locale path.