Text import with correct text parameters
Texts are only imported if the number, numbering and type of the text parameters are correct.
Localisable texts in VisiWin can contain dynamic parameters that are only formatted into a text at runtime using a formatting instruction. These formatting instructions should of course match the original text in the developer language for translated texts.
|
Setting |
Description of the |
|---|---|
|
o |
Function is switched off, check does not take place. |
|
รพ |
Function is switched on, check takes place. Incorrect texts are not imported. |
In VisiWin, each text parameter is enclosed by two @ characters. Between them are the parameter number, the parameter type and any other formatting instructions. Except for the date/time formatting, the content must not be changed.
Example
|
Localisable text definition (German) |
Description of the |
Displayed text (German) |
Localisable text definition (English) |
|---|---|---|---|
|
Should the @1n@ marked entries be deleted from a total of @2n@? |
The text contains two numerical parameters. |
Should the 5 selected entries out of a total of 123 be deleted? |
Do you want to delete @1n@ selected entries from a total of @2n@? |
|
The appointment will take place on @1ldd.MM.yyyy@! |
The text contains a parameter for date/time with a formatting instruction. |
The event will take place on 24.08.2015! |
The appointment will be held on @1lMM/dd/yyyy@! |
The first example contains two parameters: "@1n@" and "@2n@". These must both be included in the translation and must also have the same content. The order in the text may of course be different, as the grammar of the foreign language may differ from the source language.
The second example contains a parameter with the formatting "@1ldd.MM.yyyy@". The parameter must of course be contained in the translation again, but may differ in the formatting part: "@1lMM/dd/yyyy@". The identification part "1l" must be identical.