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 or upload it onto the SliTaz Community Network aka SCN.
SliTaz project Website is available in the following languages:
The website and documentation has been translated and is kept up-to-date by several contributors. For now, the actively maintained languages are Bosnian, English, French, Italian, Portuguese, Russian, Spanish and Chinese. German is on the stove, but more help is needed. Most of the communication is done through the Mailing List and the i18n group on SCN.
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 xHTML page there's always editing and proofreading to be done. Websites often move and get updated and SliTaz home made tools such as TazPanel acquire new strings depending on the new functions added to it. Over time we have developed a few ways to let you contact us and get involved in the project.
Here is a howto for translating a SliTaz website into a new language. First you need the original website page in English. You have 2 ways to get a full copy of the website: use Mercurial and clone the repository or download the latest archive in tar.bz2 format. Using Mercurial lets you update your local copy in one command and downloading directly from the repository allows you to get the page you want. So it's matter of choice, but if you want to manage a language and push changes yourself you will have to use Mercurial; here is some more info on Hg.
Clone the website or get the latest archive:
$ hg clone http://hg.slitaz.org/website $ wget http://hg.slitaz.org/website/archive/tip.tar.bz2
Now that you have a full copy of the website you can fix typos or start a new translation. The reference is English, so always copy an English page to your native language and naturally keep the website structure intact. When you're happy with your work you can send it to the community as explained beforehand.
If you're a bit afraid about sending a mail to more than 300 people on the list or becoming exposed on the forum you can send a private message to one of the i18n group members on SCN (but they might not have time to answer). Keep in mind we are a friendly community and there aren't any stupid questions.
Like said before, 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 nice graphical editor like POedit on SliTaz. That means you don't need to have programming or Linux skills to help or maintain a translation.
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 to use msginit and other gettext tools. If you want to update or complete a translation PO file you can download it from here or from Hg and then send it to the list, the forum or SCN as usual. Note that some projects are contained in the same repository such as tazpkg-notify which is part of tazpkg.
Updated: November 24, 2014 @ 03:00