Requirements

• The system should support single byte languages.
• Each user should have a user preference setting to store his/her default language .

Requirements

Language selection during the login phase:

• If no default/preferred language for the user, the language used should be taken from the browser settings.
• The login phase will have an option to change the currently selected language according to the configured supported languages.

Requirements

• The selected language should be set during the user login phase, as follows:

1. Before the user has logged into the system, based on the regional settings of the browser.
2. If the user has a default language different than the browser regional setting or the language that was manually selected in the login screen, the user default language will be used.
3. If the user wishes to change his language (via user preferences) the user should be indicated that in order for the changes to take affect he will have to re-login to the system.
4. The login screen itself should be displayed in the selected language.

Requirements

• The following regional settings should be taken from the locale setting of the browser, and should be used throughout the system:

      1. Date

      2. Time

      3. Currency (relevant label) 

      4. Numbers

Requirements

Translation scope :

• All visual strings for the end user should be translated.
• Exceptions.

Requirements

Translation:

• The system will hold a translation table allowing the system to have a unique translation for each string for each language.
• Currently the keys are long text. The system should support short keys for the RIS Web project if there is a need due to memory limitations.

Requirements

Missing translations:

• The system will have a log mechanism to document texts which do not have a translation.
• In case of a missing translation, the system will display the key of the English US translation with ‘<’ and ‘>’.

ng2-translate

ng2-translate

• Loader
• Methods
• Missing translations