...
There are a hook that allows a customer to override translations for a specific languages without altering the binary build. This feature is meant to allow a customer to enable a specific terminology to increase the user term terminology recognition from other systems.
A custom Custom text file files can be created with the name language_overrides.csv and uploaded as packages in Meridix containing lines in the format :defined below, each of these files (packages) is then loaded and used as overrides to the build in (compiled) translations.
"{langauge-code}";"{resourcepath}";"{key}";"{value}"
Example of file content:
"sv";"/Default.aspx";"lbnLoginResource1.Text";"I want to log in"
"sv";"/Default.aspx";"lbnLoginResource1.ToolTip";"I want to log in right now"
This would override the values for the Swedish translation for the login button on the login page.
...
| Info |
|---|
| This feature is only used for when customers with custom have specific requirements and are not a recommended solution for translating resourcestranslation of resources if not necessary. |
As of the current release (3.7) this functionality is only available for the user interface translations. Report content (ex: column headers) and translations used in the subscription reports are currently not overridable. This may change in upcoming releases.