Language Packs

Glossary files

Language   Download Translator, comments
Dutch Nederlands utf-8 Jip Ketel, version 4.1.0
English English

utf-8

Saurus, up-to-date
Estonian Eesti

utf-8

Saurus, up-to-date
Hungarian Magyar utf-8 Attila Németh, version 4.6.5
       
Experimental and incomplete glossaries
French Francais   Translation in progress
German Deutsch utf-8 Google Translate, to get you started, version 4.4.3
Italian Italiano utf-8 Google Translate, to get you started, version 4.4.3
Japanese 日本語   Translation in progress
Korean 한국어 utf-8 Google Translate, to get you started, version 4.4.3
Portuguese Português utf-8 Google Translate, to get you started, version 4.4.3
Russian Русский utf-8 Saurus, may need updating
Spanish Español utf-8 Google Translate, to get you started, version 4.4.3 

How to install

Import any of these glossaries into your copy of Saurus CMS from Admin > Languages > Glossary.

Make your own translation

Didn't find your language? Here's how to add your own translation.

First you need an existing glossary file. Download one from this page or use the following steps to export it from your copy of the software: 

  1. Log in to the site administration interface and go to Admin > Languages > Glossary.
  2. Choose English or any appropriate source language you wish to translate from in the dropdown at right.
  3. Choose Export.
  4. From the popup window, choose Type: Default.
  5. Push Save to save the glossary contents as CSV file.

With glossary CSV file:

  1. Open it and change the strings in TRANSLATION column. We suggest to use MS Excel or OpenOffice Calc for the job.
  2. In Saurus CMS, create new target language in Admin > Languages > Languages page.
  3. When move your mouse over the languages links you can see the link parameters in browser’s status bar. Check the “keel_id” parameter, for example for English language it has a value of “1”.
  4. In your CSV file, change the first number in the “Checksum” row to your language id, e.g. [CHECKSUM= [your language id]:18:826]
  5. Rename your CSV file to “language[your language id].csv”.
  6. Make sure the CSV text file encoding is ASCII and not UTF-8 or anything else - CMS does not detect automatically file encoding and expects ASCII encoding.
    Make sure the CSV file is in UNIX file format (Windows file format is supported starting from version 4.4.3). 
  7. That’s it! You can now import the translations into system glossary in Admin > Languages > Glossary page.

If you wish to donate your translation to the project, please write to saurus at saurus dot info.