The following applies to all event lists - AEL, LEL and Table View.)
column title translations are contained within 2 localisation
2 files appear to contain the same things but they are actually used
- The AEL will consistently show the saved translations for the view regardless of the language used in the browser because the translations had been saved as the column title.
Using En_US locale
- (7.3.1 defect) When creating a new view, fields that are selected by default have English column titles English translation remains even after removing and adding back these fields can be worked around as follows:
- Remove fields
- Save view
- Reopen view
- Reselect fields
- Uncomment needed fields in columnheadings_<lang>.properties
- The content are commented out by default. If content has been uncommented and WebGUI restarted, the translations will be used as the column title in the AEL per browser language setting.
- Completely overrides view's column title setting.
- View Builder will show either the translated column title from defaultcolumnheadings_<lang> or the customised column title (if changed from the default), but it is ignored when the view is used in the AEL.
WebGUI 220.127.116.11 TF002
- Out-of-the-box views are not translated because the column titles in the config file are in English
- Uncomment the translations in columnheadings_<lang> to get the translated column titles but note the side-effect as described above.
- Field names in the AEL's Information (Alert Status) window displays translations from defaultcolumnheadings_<lang>.properties.
- Mismatch - the table heading in this window states "Field", but it displays translated column title.
- If translations in columnheadings_<lang> are not commented out, the event list will show the column title as saved in the view config file, but the Information window will display fields translated using defaultcolumnheadings_<lang>.properties
translated views via WAAPI
- If the view is to be monolingual, then just create the view using the desired language for the column title.
- If the view is to be multilingual, create the view as usual, and then uncomment the translations in columnheadings_<lang> (note the side-effects of doing so)
- Translate custom fields/columns in the ObjectServer by adding the field names + translations into the defaultcolumnheadings_<lang> and/or columnheadings_<lang> localisation files for the target languages.
- In general, this applies for all fields that are not specified in the localisation files.