Translations in Spaix products

Further background information as guidance for dealing with translations vs. user interface and summarizing the topic of translations in Spaix..

1)    Translations

-    Are used for the basically build-in Spaix GUI elements.

-    Are stored in vsprogram.mdb (or corresponding SQL) database in table ProgramTranslation 

-    Master-source is VSX, usually customers provide up to now untranslated new translations to VSX. However, these gaps are expected to be filled in the future by AI-supported translations.

-    Updated translations are usually provided regularly with program updates, therefor vsprogram.mdb must not be changed by customers

-    Existing translations are usually not changed, expect there are distinguishable reasons

1.5)     Customer specific program translations 

-    Existing program translations can be customized means overridden by additional license TranslationManager which enables customers to use additional table ApplTranslation in vsSpaix.mdb (or corresponding SQL) database. If given for certain RESIDs these translations are superior against ProgramTranslation table.

-    Max. length of translations should be considered in aspects of used panel/controls if length visibly differs from existing translations

-    At last there is a max. 150 characters length possible

-    However it is possible to override our standards with available module TranslationManager in general this is not recommended as translations can be re-used in different places of the programs. So if you would change an existing translation with the intention of showing a more appropriate translation in one place, there may be other places of the same translation in slightly different context where this leads to inappropriate translations. Therefore this possibility should be used with great care.

Sample: VSX customer who has licensed this module the VSX default “Accessories” is replaced with the term “Valves and Pumps Accessories”.

2)    Data Translations

-    Are usually translations for data users or customers added into Spaix database (like component names)

-    Have to be maintained by users themselves, some default data like fluid names should be already available

-    Are stored in vsSpaix.mdb (or corresponding SQL) database DataTranslation

It is possible to automatically retrieve all possible values which can be translated via the Create RESIDs from existing objects button but to prevent unnecessary data in translation database it should be used only when really necessary for mass translations. So it is up to the user to collect necessary data values which should be translated and add them into DataTranslation table. A good approach would be to do this in a Excel spread sheet which can be imported into Spaix.

3)    Description Translations

-    Are translations for text data, users or customers added into Spaix database (e.g. hint-, short- and long texts)

-    Have to be maintained by users themselves

-    Are stored in vsSpaix.mdb (or corresponding SQL) database Description

-    Can be plain text or RTF formatted text, however RTF formatting options are limited means only basic RTF formatting is supported in Spaix (e.g. no tables)