This page (revision-6) was last changed on 09-Feb-2023 10:35 by Lilia Urtan

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
6 09-Feb-2023 10:35 1 KB Lilia Urtan to previous
5 26-Nov-2021 10:22 1 KB Lilia Urtan to previous | to last
4 26-Nov-2021 10:22 1 KB JMyers to previous | to last
3 26-Nov-2021 10:22 1 KB JEscott to previous | to last
2 26-Nov-2021 10:22 1 KB JMyers to previous | to last
1 26-Nov-2021 10:22 519 bytes JMyers to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 2 changed one line
The language of the system can be tailored to suit your needs. Translation can vary from minor terminology changes to full multilingual support.
The language of the system can be tailored to suit your needs. Translation can vary from minor terminology changes to full multilingual support.
At line 4 added one line
The languages that are used in the application are defined on the Define Translation Languages form ([IMLA]). Translations cascade down from the highest applicable language (based on Seq #) to the base language which is USA English. This means that if an expression is not translated, you will still see meaningful information - in English.
At line 5 changed one line
The languages that are used in the application are defined on the [IMLA]-Define Translation Languages form. Translations cascade down from the highest applicable language (based on Seq #) to the base language which is USA English. This means that if an expression is not translated, you will still see meaningful information - in English.
When you log in, your personal information is used to determine which languages are applicable to you. It depends on your language of preference, country and role. All user interface components are translated appropriately for you. On forms containing fields that are translatable, you will see 2 fields - one for the primary language and one for the translation. In the example below, displayed values are translatable so you will see two descriptions for each saved value.
At line 7 changed one line
When you log in, your personal information is used to determine which languages are applicable to you. It depends on your language of preference, country and role. All user interface components are translated appropriately for you. On forms containing fields that are translatable, you will see 2 fields - one for the primary language and one for the translation. In the example below, displayed values are translatable so you will see two descriptions for each saved value. When the lexicon is used, an English user will see an English pick list and a French user will see a French pick list.
When the lexicon is used, an English user will see an English pick list and a French user will see a French pick list.
At line 9 removed 2 lines
End user is able to update ENG field on IMFDH by right click on the main prompt and entering the translation in the 'Fill in translations below' dialog.
Once it is added the user can update or delete translation in IMLA for corresponding context.
At line 12 removed one line
To add a translation for the form's column detail, use the translation popup menu on the form itself. It is available for any column where the Translation Allowed is turned on in IMCD.
At line 14 added one line
[{If var='loginstatus' contains 'authenticated'
At line 17 removed one line
At line 19 changed 2 lines
![Notes|Edit:Internal.TRANSLATION+CAPABILITY]
[{InsertPage page='Internal.TRANSLATION+CAPABILITY' default='Click to create a new notes page'}]
![Discussion|Edit:Internal.TRANSLATION+CAPABILITY]
[{InsertPage page='Internal.TRANSLATION+CAPABILITY' default='Click to create a new discussion page'}]
}]