Languages are used to denote which language the guest prefers to speak and to determine if the folios and mailings should be printed in different languages depending on the guest language code. Language codes can also be used to translate interface texts, messages, and folios into that default language. Select System Configuration > Profile > Geographical Data > Languages to access the Languages screen.
Language Code. A user definable code that identifies a language (E, F, G, I).
Description. The full text language name associated with the code (English, French, German, Italian).
Trans Language. This attribute is required for the Translation Studio program.
Select Languages to display a list of the existing language codes. Select New to create a new code, or Edit to change a code. The Languages - New/Edit screen displays.
Language Code. Enter a language code that easily identifies the language. When entering language codes, Interfaces normally can only translate one character in the translation tables. Although OPERA can support more, it is recommended that you limit the language codes to one character.
Description. Enter the name of the language.
Translation Language . Select the translation language and description from the list of values. If no translation language is selected, OPERA internally defaults to English for that language.
Report Date Language. Select the down arrow to choose the report date language from the list of values. Date elements that might be spelled out, like the day-of-week or the month, will be represented correctly in the report language if this field is filled.
The list of values shows both the Locale language code (ISO 639) and the Oracle NLS language, as applicable. For BI Publisher reports (see Stationery Editor for details), you can specify a variation (called the Locale language) of base languages that differ across geographical, political, and cultural regions. For example, Brazilian Portuguese—Portuguese/Brazil (pr_BR), versus Portuguese that is spoken in Portugal—Portuguese/Portugal (pt_PT). For non-BI Publisher reports (i.e., Oracle reports), the language listed in the NLS Language column will be used.
Note: When BI Publisher reports are used, and are configured in languages other than English, a Language Locale MUST be specified as Report Date Language. Standard Report Date Language codes without a Locale attribute will not translate dates for BI Publisher reports.
Address Doctor Script. (Only available with AddressDoctor V5) Define a specific language for the script that AddressDoctor should use to return the results. The options are:
Note: If the Address Doctor Script and/or Address Doctor Language are selected for a specific language code, address records that use that language code are cleansed using the language-specific script and language, rather than the globally set script and language defined in Configuration > Profile > AddressDoctor Setup. Address records that do not use the Address Doctor Script and/or Address Doctor Language in the address are cleansed with the globally set script and language.
Address Doctor Language. (Available when either ADDRESSDOCTORV4 or ADDRESSDOCTORV5 is selected as the default address cleansing system via the application setting Profiles > Address Cleansing System.) Select the Address Doctor Language from the list of values. If no Address Doctor Language is selected here, OPERA will default to the language selected under Configuration > Profile > Address Doctor Setup.
ADDRESSDOCTOR4 has the following languages available for selection:
For ADDRESSDOCTOR5, the following languages are available:
Note: The Address Doctor documentation contains more details on the required settings.