Saurus 4 Translations

You can import those glossary files into your CMS from Admin > Languages > Glossary page. Choose the appropriate encoding before importing.
 
Language   Download Translator, comments
Dutch Nederlands utf-8 Jip Ketel, version 4.1.0
English English iso8859-1 | utf-8 | convert.. Saurus, up-to-date
Estonian Eesti iso8859-4 | utf-8 | convert.. Saurus, up-to-date
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

Note: Use our encoding conversion script for converting the existing language files to the different encoding.

Translating the product

To translate Saurus CMS user interface first you need an existing language file. You can download one from above in this webpage or use the following steps to export file from your existing CMS installation: 

  1. Log in to 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 the language 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.