Internationalization

The main goal of SliTaz is to provide full support for a given language, including the website, official Wiki documentation, a dedicated forum and all SliTaz related projects such as the LiveCD GUI builder.

Translation is a community effort and everyone can help. You're welcome to join the team! You can find more pot files on Hg, just pick one up, translate it and send it to the mailing list.

SliTaz website is available in the following languages:

EnglishFrançaisDeutschEspañolPortuguêsРусский

Information

The website and documentation has been translated and is kept up-to-date by several contributors. The actively maintained languages are English, French, German, Spanish, Portuguese and Russian. Most of the communication is done through the Mailing List.

Some additional languages can be installed through the Package Manager, but we are not able to provide support and documentation. SliTaz is a community based project, everyone can help out and is more than welcome to join us.

How to participate

From fixing typos to translating a full HTML page there's always editing and proofreading to be done. Websites often move and get updated and SliTaz tools such as TazPanel acquire new strings depending on the new functions added to it.

For sending translations or requesting a new language you can join the SliTaz Mailing List.

Website translation

Here is a howto for translating the SliTaz website into a new language. The reference is English — always copy an English page to your native language and keep the website structure intact. Clone the website repository or get the latest archive:

$ hg clone https://hg.slitaz.org/website
$ wget https://hg.slitaz.org/website/archive/tip.tar.bz2

When you're happy with your work you can send it to the mailing list or join SliTaz Core on Signal to coordinate directly with the team.

System translation

The goal is to provide full language support — not only with the website or forum, but with the system itself. Everything can be translated from menu items to SHell scripts and GUI boxes. For this we use standard gettext POT files.

Each translation of a sub-project has its own file named with a language prefix, example: pt_BR.po or fr.po. This PO file can be translated with a graphical editor like POedit on SliTaz.

If a PO file for a language doesn't exist you can create one yourself or ask a contributor to do it for you and commit the new file to Hg. For each project you will find a README file with translation instructions.