Role required: admin. |
To localize a choice list, please complete the steps below:
Translated choice option form fields
| Field | Description | |
|---|---|---|
| Table | Specify the table to which this choice option is related to.
| |
| Column | Specify the column to which this choice option is related to.
| |
| Title | Type the translation of the source field there. | |
| Language | In there, specify the two-symbol name of the language (ru, en, and so on). Generally, references to languages are stored in the Languages (sys_language) table. | |
| Value | Type the same value as specified for the source field. | |
| Order | Enter the number to define the option order in the choice list. | |
| Hint | Text hint. This field is not mandatory. |
Repeat this step for the rest options of the list.
Please check before started that all necessary languages are created in the Languages (sys_language) table. |
To localize any field of the Translated Text type (except for the choice list option whose translation was described above, or special interface elements like flash messages or Condition Operators), please complete the steps below:
Translated text form fields
| Field | Description |
|---|---|
| Language | In this reference field, specify the language of the translation (ru, en, and so on). Generally, references to languages are stored in the Languages (sys_language) table. |
| Value | Type the translation of the source field there. |
| Column | In this reference field, specify the column containing the field being translating. |
| Record | Type the ID of the record which should be translated. |
To localize static interface elements, such as welcome messages, informational or warning messages, some other kind of messages, there are two tables implemented containing source messages and their translations,
Field | Type | Description |
|---|---|---|
| id | Big Integer | The ID of the message. |
| category | String | The category of the message (for example, app). |
| message | Text | The text of the message. |
Field | Type | Description |
|---|---|---|
| id | Reference | Reference to the Source Messages (source_message) table. |
| language | String | Two-symbol name of the language (ru, en, etc). |
| translation | Text | The translated message. |
These two tables are bound by ID; it means that every message in the Source Messages (source_message) table has a unique ID, and its translated version in the Messages (message) table has the same ID.
For example, the message "Login" in the Source Messages (source_message) table has ID 15596431050000002. Moreover, the message "Логин" has the following prerequisites in the Messages (message) table:
| ID | 15596431050000002 |
| language | ru |
So, if you want to add some new messages, you have to add them to both tables as well, in compliance with IDs order and in all the languages you need.
To do this, please complete the steps below:
Please keep in mind that the IDs of the original message in the Source Messages (source_message) table and the localized message in the Messages (message) table must be the same to prevent malfunction. Also, the language field must be populated, as well. |
Please do not change original messages in the Source Messages (source_message) table, it can cause malfunction on the instance. If you need to make changes in any source message, then create a copy of it in the Messages (message) table with the desired text and fill in the Language field with the 'en' value. |
In SimpleOne, we have the SimpleMessage API class with the getMessage() message in it which is taking in an original message from the Source Message (source_message) table and returns a message in the user's language that is set as default in the system. To read more, please refer to the relevant article: SimpleMessage.