WoodWing Help Center

Support for non-English languages in Elvis 4 Server

Support for non-English languages in Elvis 4 Server

When the main language of your content and metadata is not English, you can explicitly configure your preferred language or 'locale' in the config.properties.txt file.

Note: If you change this setting in an existing installation, you have to run an index updater (without any options selected) to make sure the search engine uses the correct language analyzers.

Doing so will allow the Elvis server to tune its behavior to that specific language. Search results will be more accurate when the text analysis is tuned to the language of the content and metadata stored in Elvis.

#
# Default locale to use when none is supplied by a client connected to the system.
# When you specify 'default', the locale provided by the operating system is used.
# This may not always be correct, so it is better to specify a locale explicitly.
#
#    locale=en_US
#
# Choose one of the following supported locales:
#
#   en_US, de_DE, fi_FI, fr_FR, it_IT, ja_JP, ko_KR, nl_NL, pl_PL, ru_RU, th_TH,
#   tr_TR, zh_CN, zh_TW
#
# When the 'analyzerLocale' config property is empty, this locale will be used to
# select the Lucene default analyzer that is used to index and search text.
#
# Important: when you change the locale or the analyzerLocale, all metadata needs to be
# re-indexed. Otherwise the indexed terms won't match the terms produced by analysis
# of the search query. Re-indexing metadata can be done by running an asset index-
# update with no options selected.
#
# This locale is also used to determine the primary language for Mac encoding
# detection in non-XMP metadata (for example IPTC metadata saved in MacRoman).
#
locale=default

#
# This controls the Lucene default analyzer that is used to index and search text.
#
# When empty, the setting from the 'locale' config property will be used, which
# defaults to the locale configured in the operating system on this server.
#
# Important: when you change the locale or the analyzer, all metadata needs to be
# re-indexed. Otherwise the indexed terms won't match the terms produced by analysis
# of the search query. Re-indexing metadata can be done by running an asset index-
# update with no options selected.
#
analyzerLocale=
Was this article helpful?
0 out of 0 found this helpful / Created: / Updated:
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.