Difference between revisions of "Features/Internationalization"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
| Line 25: | Line 25: | ||
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. | ||
Note that the general GUI and solution elements are handled independently, and are not required by each other. | |||
== Configuring new languages == | == Configuring new languages == | ||
Revision as of 14:13, 11 February 2013
Scope of I18N
The following elements in TempusServa may have seperate language settings
- Standaard GUI elements
- Solution specific elements
Actviating I18N
Configuring I18N for 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.
Configuring new languages
Options include
- Pagers
- Buttons
- Messages
- etc.
The languages are controlled through: Designer > Ressources > Language