If your
application accesses data in more than one language, you must specify the
language of each particular query at query time. For example, if you set the
language ID of a property to
ja, any search run against that property must also specify
the language id
ja, or text management features such as word breaks will
not function correctly.
The MDEX Engine (Dgraph) determines the language of the text of a query according to the following rule:
Note
If all your data is in the same language, set the default language of the MDEX Engine to that language. For information about how to do this, see Assigning Language IDs Globally (per MDEX Engine).
Some properties will be searched by queries in different languages; that is, by queries with different language IDs. For example, a Partnumber property might be searched for in both Japanese and English.
In
such a case, you can create a separate Partnumber property for each language.
Each property name must be appended with the applicable language ID code; for
example:
Partnumber_ja (for Japanese searches) and
Partnumber_en for English.
