When you index multiple languages in a single MDEX, the schema generated is similar to the schema that would be generated in the multiple-MDEX case for the first locale listed in the /atg/endeca/ApplicationConfiguration
component’s locales
property. The data records include separate records for each of the listed locales, with each data record including a product.language
property that identifies the language of the record. The language name is given in its own language. For example, the value for the German language is Deutsch.
The dimension value records are similar to the set of records that would be generated for each language in the multiple-MDEX case, but the records generated by the /atg/commerce/endeca/index/RepositoryTypeDimensionExporter
component contain additional properties for the translated display names of the repository item types. These properties are named displayName_
language
C
ode
, where language
C
ode
is the two-letter language code associated with one of the specified locales. For example:
<PROP NAME="displayName_en"> <PVAL>Product</PVAL> </PROP> <PROP NAME="displayName_de"> <PVAL>Produkt</PVAL> </PROP> <PROP NAME="displayName_es"> <PVAL>Producto</PVAL> </PROP>
Note that the property names shown in the example above are appropriate for use with CAS-based deployment templates, and assume that the name changes specified in propertyNameReplacementMap
property of the DimensionDocumentSubmitter
component have been applied. See RecordStoreDocumentSubmitterfor more information.
If the multiLanguageSynonyms
property of the RepositoryTypeDimensionExporter
component is set to true
, then additional Guided Search record properties are generated to indicate that all translations of the same repository type are synonyms for searching. For example:
<PROP NAME="dimval.search_synonym"> <PVAL>Product</PVAL> <PVAL>Produkt</PVAL> <PVAL>Producto</PVAL> </PROP>