Translation table is a database table that contains the translation data of the dictionary. DatabaseDictionary dictionary component uses this format. The format of the row is:
Field | SQL Type | Index | Description |
---|---|---|---|
Native | VARCHAR(X) | yes | The native language. This field must have a primary unique index. |
Form | VARCHAR(X) | yes | Optional. The name of the form (frame) where the string belongs to. This field exists only in the context sensitive dictionaries. |
Component | VARCHAR(X) | yes | Optional. The name of the component where the string belongs to. This field exists only in the context sensitive dictionaries. |
<language1> | VARCHAR(X) | The first supported language | |
<language2> | VARCHAR(X) | The second supported language | |
... | ... | ||
<languageN> | VARCHAR(X) | The last supported language |
Where
language? is the English name of the language (e.g. Finnish, German, etc). The
dictionary components access the fields by the index. That's why the actual name of the
column is not used.
X is maximun size of the translation. In most applications 100 is quite enough.
Use Language Manager or your database tool to create and edit translation files.
The following SQL script creates a translation table containing the native language, English and Finnish.
CREATE TABLE TranslationTable ( Native VARCHAR(128), English VARCHAR(128), Finnish VARCHAR(128) );
CREATE UNIQUE INDEX Native ON TranslationTable(Native);
The following SQL script creates a context sensitive translation table containing the native language, context information, English, German and French.
CREATE TABLE TranslationTable ( Native VARCHAR(128), Form VARCHAR(32), Component VARCHAR(32), English VARCHAR(128), German VARCHAR(128), French VARCHAR(128) );
CREATE UNIQUE INDEX Native ON TranslationTable(Native,Form,Component);