Language Configuration
The file config\languages.xml defines various languages that are known to Commerce Server Business Desk and which are available for modules to use. This information is made available to modules through the xmlGetLanguages()function in ASPUtil.asp. This routine returns an XML document resulting from an XSL transform of this file.
XML Structure
<Languages>
<Languagecollation browser_language display_name iso639x primary_language word_breaker />
. . .
</Languages>
Valid values are the LCIDs of the languages for which wordbreakers are provided by SQL Server.
The hexadecimal numbers in the below table are valid values. The text represents the wordbreaker for that language.
0 Neutral 0x0804 Chinese_Simplified
0x0404 Chinese_Traditional
0x0413 Dutch
0x0809 English_UK
0x0409 English_US
0x040c French
0x0407 German
0x0410 Italian
0x0411 Japanese
0x0412 Korean
0x0c0a Spanish_Modern
0x041d Swedish_Default
Languages
This required element contains the language configuration information for Commerce Server Business Desk.
- Parent Element
None (document root). - Required Child Elements
None. - Required Child Elements
Language - Data
None.
Attributes
None.
Remarks
To be meaningful, the Languages element must contain one or more Language elements. Multilingual aspects of the Product Catalog System are configured using this information. Examples include: the set of languages associated with a multilingual property, or the set of default values for that property, and the set of languages associated with a catalog. Usually interaction with the catalog occurs within the context of a certain language, either through a user interface selection or a programmatic setting. This means that all multilingual properties will expose (to a user interface) or return values associated with the current language selection or setting for that catalog.
Return to XML Structure
Language
This optional element contains the configuration information about a single language known to Business Desk.
- Parent Element
Languages - Required Child Elements
None. - Optional Child Elements
None. - Data
None.
Attributes
| Attribute | Description |
|---|---|
| collation | Specifies the SQL collation identifier for the corresponding language.
Optional. Legal values: Valid SQL collation identifiers. Default value: None. If this attribute is not specified, as is the default, collation will default to the SQL default for the corresponding language. |
| culture_name | Specifies the culture name and follow the RFC 1766 standard in the format "<languagecode2>-<country/regioncode2>", where <languagecode2> is a lowercase two-letter code derived from ISO 639-1 and <country/regioncode2> is an uppercase two-letter code derived from ISO 3166.
Required. Legal values: Valid RFC 1766 culture identifiers. For example, U.S. English is "en-US". Some culture names have prefixes that specify the script; for example, "Cy-" specifies the Cyrillic script, "Lt-" specifies the Latin script. |
| culture_code | Specifies the locale identifier (or LCID) following the RFC 1766 standard. This is represented as a four digit hex value prefixed with “0x”.
Required. Legal values: Valid RFC 1766 locale identifiers. For example, U.S. English is "0x0409". |
| display_name | Specifies a display name for the corresponding language.
Required. Legal values: Valid strings. Default value: None. For example, the display name for US English is "English (United States)". |
| iso639x | Specifies the ISO 639 two-character language code (plus an optional third character as used by Windows to identify sublanguages) for the corresponding language.
Required. Legal values: Valid ISO 639x language codes. Default value: None. For example, the iso639x code for US English is "ENU". |
| word_breaker | Specifies the SQL word breaker to be used for the corresponding language.
Optional. Legal values: Valid SQL word breakers. Default value: None. If this attribute is not specified, as is the default, the word breaker will default to the SQL default for the corresponding language. |
Remarks
For the language configuration to be meaningful, at least one Language element must exist within the Languages element.
Return to XML Structure
Copyright © 2005 Microsoft Corporation.
All rights reserved.