SiteStudio Online Documentation

For more information contact us

Language Support in SiteStudio

Starting with SiteStdio 1.7 RC2 (including versions 1.7rc2, 1.7 and 1.7.1), language support has been simplified.

For additional information, read about configuring additional languages in SiteStudio before 1.7 RC2 (including versions v 1.7 RC1 and 1.6x)

Additional languages in SiteStudio 1.7 RC2 and later are configured using the LANG_LIST property of the [SS_DIR]/psoft_config/masonry.properties file and language file translated into the corresponding language that should be located in the [SS_DIR]/psoft_config/langs/ directory. The property mentioned above should contain a list of locales (languages) available to SiteStudio users. Each locale definition should be separated by space from other locales. The first element of the LANG_LIST property is treated as a default SiteStudio locale.

Syntax:
LANG_LIST=<Language1> <Language2> ... <LanguageN>

Here: <Language>=<LanguageCode>_<CountryCode>_<Encoding>
where:
         <LanguageCode> - is a valid ISO Language Code. These codes are the lower-case two-letter codes as defined by ISO-639. You can find a full list of these codes at a number of sites, such as: http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt.
         <CountryCode> - is a valid ISO Country Code. These codes are the upper-case two-letter codes as defined by ISO-3166. You can find a full list of these codes at a number of sites, such as: http://www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html.
         <Encoding> - is a valid encoding using which the language file was created.

You can find a full list of these aliases at a number of sites, such as: http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html.

After adding a language definition into the LANG_LIST property, you have to copy the file [SS_DIR]/psoft_config/langs/lang.properties into a file [SS_DIR]/psoft_config/langs/lang_<LanguageCode>_<CountryCode>[_<Encoding>].properties, translate all properties of the file into the corresponding language and restart SiteStudio, if it is running, to apply changes.

 

Example of a language configuration in SiteStudio.

Lets assume you want to configure French and Russian languages in SiteStudio with the iso-8859-1 and windows-1251 encodings for language files.
To create the language entries for the LANG_LIST property:

  1. Look into the following documents iso639.txt, ISO_3166.html and encoding.doc.html, find the corresponding language, country and encoding codes for French and Russian languages and create an entry for each language.
  2. When done, you should get the following:
             for French: fr_FR_ISO8859_1
             for Russian: ru_RU_CP1251

    So the final LANG_LIST property of the masonry.properties file will look as follows:

      LANG_LIST=en_US_ISO8859_1 fr_FR_ISO8859_1 ru_RU_CP1251

    This configuration defines English language as default and additional French and Russian languages.

  3. Copy the file psoft_config/langs/lang.properties into psoft_config/langs/lang_fr_FR_ISO8859_1.properties for the French language
  4. Copy the file psoft_config/langs/lang.properties into psoft_config/langs/lang_ru_RU_CP1251.properties file for the Russian language.

After translating both files to the corresponding language and restarting SiteStudio you should be able to use newly added languages.

NOTE1: You can omit the encoding of the file if it is ISO-8859-1. So you can simplify the LANG_LIST property as follows:

LANG_LIST=en_US fr_FR ru_RU_CP1251
Also the above config requires renaming the file psoft_config/langs/lang_fr_FR_ISO8859_1.properties into psoft_config/langs/lang_fr_FR.properties file.

NOTE2: in case you defined new locale in the LANG_LIST property, but did not create corresponding language file, all tokens will be retrieved from the default psoft_config/langs/lang.properties file.

NOTE3: SiteStudio treats Arabic (LanguageCode: ar), Hebrew (iw) and Urdu (ur) as RTL languages, i.e. RTL tags will be added onto appropriate places for sites created with any of those languages.

International Characters on Buttons and in Headers

Default SiteStudio fonts for some languages may not display all language characters properly. If this is the case, you can add your fonts supporting your national symbols to the SiteStudio defaults To do it:

  1. Add your fonts to /usr/java/jdk/jre/lib/fonts/.
  2. Create a backup folder for it and a script that will place them back as H-Sphere updates might override custom fonts (for H-Spehre users only).
  3. Create (if there isn't any) a fonts.properties file in the SiteStudio folder.
  4. modify it and re-map default SiteStudio fonts with custom ones in the way as follows.
    Example:
    tr.Amelia_BT=Arial Turkish
    tr.Turkey_Sandwich=Turkey Sandwich Turkish

In the example above SiteStudio will use "Arial Turkish" font each time when font Amelia BT is selected and font Turkey Sandwich Turkish instead of Turkey Sandwich. Use only real font names (font face names, not the filenames).

Examples for Russian fonts:

ru.Amelia_BT=Amelia BT Cyr
ru.FetteFraktur=DrPoDecorRu

Examples for Chinese fonts:

zh.Soopafresh=CTKaiTiSJ
zh.Cetus=MingLiU
zh.Epilog=STXingkai
zh.FetteFraktur=KaiTi_BG2312
zh.Futured=FangSong_GB2312

The fonts will be remapped for the language interface (when users choose the language on the site settings or on the login page), although in SiteStudio users will see our font names (Amelia, Cetus, etc.).

Fonts to be remapped (otherwise some charachters may be not displayed properly):
Amelia_BT=
Cetus=
Epilog=
FetteFraktur=
Futured=
Impact=
Soopafresh=
Turkey_Sandwich=
Intrepid=
Intrepid_Bold=
Zurich_LtXCn_BT=


See also

Product Page
Online Demo
FAQ
SS Doc Home



Copyright 1998-2007. Positive Software Corporation.
All rights reserved.