Translator component translates page contents with help of language files.
The choosen language is rememberd for the next users visit.

Examples

Example 1: Include localisation tools

Include the localisation tools and use the defined languages and translations files.
Allows users to select their language and changes the gui language on the fly.

Example 2: Mark contents as translateable with translation file

By useing the swac_lang HTML attribute you can define the content of tags and attributes as translatebale. This example shows on which tags and attributes translation is useable.

Example 3: Useing appwide language entries

If you want to use a general translation without need to use a prefix, you can define an app language. This can be used to translate even attribute names.

Example 4: Change component language with Translator

Many components come with their own language files and use language marks in their templates. With the Translator component these areas translated too.

Example 5: Overwriting component default language entries with custom translations

The translations delivered by the components can be overwritten. This example shows how.

Example 6: Language dependend locale formats

Format of numbers and dates can be different from country to country.
This aspect can be held by the language files, too.