QAD .NET User Interface Overview > QAD Messaging > Using the Translation Option
  
Using the Translation Option
The Description fields for most component-based records support a translation option. The initial description is essentially language neutral. However, clicking the Translation button to the right of the Description field copies that description into a record for each available language.
The Use Language Specific Object Description field in Change System Settings determines whether the system displays translated descriptions in the user’s native language. If this field is selected, field descriptions are displayed in the language associated with a user’s ID in User Maintenance, provided that translated descriptions are loaded or entered for this language. If the Use Language Specific Object Description option is enabled, the system also retrieves translated descriptions when the user runs API queries.
When the Use Language Specific Object Description option is enabled system wide, you can disable it in Change System Settings for a specific user. See User Guide: QAD System Administration for more information on system and user settings.
Note: One of these languages is the language of the current domain. While most descriptions are likely to be entered in that language initially, the description is linked to a language only by setting up the translations.

Translating Account Description
If you choose to use this feature, you must develop your own policies to ensure that the translation of descriptions is completed for the languages that need to be supported in your organization.
Some financial data is also displayed and accessed in other operational functions. These functions do not support multiple language-dependent descriptions. When only one description exists, it is always used in the operational functions.
Note: Unless you are using a Unicode database, some restrictions exist on which languages can be used in a single database. See the appropriate installation guide for information on the Unicode database deployment.