A language can be set for each standard attribute.
A Property Description Record (PDR) has an mdex-property_Language field that specifies the language of that standard attribute. This field takes one of the supported language codes listed in Supported languages.
<mdex:record> <mdex-property_Key>Beschreibung</mdex-property_Key> <mdex-property_Type>mdex:string</mdex-property_Type> <mdex-property_Language>de</mdex-property_Language> ... </mdex:record>
If it is not explicitly set, mdex-property_Language defaults to the unknown language identifier when the standard attribute is created by the system.
For example, your data may have an English standard attribute called Description with its language code set to en, and a Spanish attribute called Descripción with a language code of es. In this case, because an individual record can have both English and Spanish text, you can see that an attribute language code is more appropriate than a per-record language code.
Typically, you set the mdex-property_Language property when creating the record schema for your data set. However, the language code can later be changed via the Configuration Web Service's updateProperties operation.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.endeca.com/MDEX/config/services/types/2/0" xmlns:ns1="http://www.endeca.com/MDEX/config/XQuery/2009/09"> <soapenv:Header/> <soapenv:Body> <ns:configTransaction> <ns:updateProperties> <ns1:record> <mdex-property_Key>Province</mdex-property_Key> <mdex-property_Language>fr</mdex-property_Language> </ns1:record> </ns:updateProperties> </ns:configTransaction> </soapenv:Body> </soapenv:Envelope>
Keep in mind that changing the value of mdex-property_Language for an existing attribute will force a regeneration of the text search indexes, which is a potentially time-consuming operation.