When you index multiple languages in a single MDEX, the schema records generated are the same as the records 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 generated 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 consist of the same 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 dimval.prop.displayName_language-code, where language-code is the two-letter language code associated with one of the specified locales. For example:

<PROP NAME="dimval.prop.displayName_en">
  <PVAL>Product</PVAL>
</PROP>
<PROP NAME="dimval.prop.displayName_de">
  <PVAL>Produkt</PVAL>
</PROP>
<PROP NAME="dimval.prop.displayName_es">
  <PVAL>Producto</PVAL>
</PROP>

If the multiLanguageSynonyms property of the RepositoryTypeDimensionExporter component is set to true, then additional Endeca 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>