Difference between revisions of "Features/Internationalization"

From TempusServa wiki
Jump to navigation Jump to search
old>Admin
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Scope of I18N ==
== Usage ==
TS supports multiple languages in the same solutions.
 
Out of the box includes Danish and English, but it is easy to add additional languages,
 
The following elements in TempusServa may have seperate language settings
The following elements in TempusServa may have seperate language settings
* Standaard GUI elements
* Standaard GUI elements
* Solution specific elements
* Solution specific elements


=== Instructions ===
Enabling I18N will allow users to select their language or set it on their user profile
* Designer > Modules > Configuration > languageUseI18N = true


== Actviating I18N ==
== Multilanguage solutions ==
 
 
 
 
== Configuring I18N for solutions ==
Options include
Options include
* Field names
* Field names
Line 26: Line 28:
Each translation should be seperated by a new line. long texts can be split into multiple lines, that may or may not be handled with linebreaks.
Each translation should be seperated by a new line. long texts can be split into multiple lines, that may or may not be handled with linebreaks.


== Configuring new languages ==
Note that the general GUI and solution elements are handled independently, and are not required by each other.
 
== Adding custom languages ==
Options include
Options include
* Pagers
* Pagers

Latest revision as of 12:53, 10 November 2024

Usage

TS supports multiple languages in the same solutions.

Out of the box includes Danish and English, but it is easy to add additional languages,

The following elements in TempusServa may have seperate language settings

  • Standaard GUI elements
  • Solution specific elements

Instructions

Enabling I18N will allow users to select their language or set it on their user profile

  • Designer > Modules > Configuration > languageUseI18N = true

Multilanguage solutions

Options include

  • Field names
  • Lookup values
  • etc.

The languages are controlled through: Solution > [SOLUTION] > Wizard > Internationalization

Translations should be prefixed with the desired language code

en:This is the english translation

ge:Dies ist der Englisch-Übersetzung

Each translation should be seperated by a new line. long texts can be split into multiple lines, that may or may not be handled with linebreaks.

Note that the general GUI and solution elements are handled independently, and are not required by each other.

Adding custom languages

Options include

  • Pagers
  • Buttons
  • Messages
  • etc.

The languages are controlled through: Designer > Ressources > Language