You can explicitly provide search text response languages, but if you don’t, Merchandising uses the language a user selects from the Search Text Language drop-down list, which means that you’ll see only the products and SKUs that are indexed in the same language as the search text. A search for “robe” when the search text and search text response languages are English will return the silk and terrycloth coverings that one wears over pajamas.
Because you can specify one search text language at a time, if you want a test to find products and SKUs in multiple languages, you should specify multiple response languages. Consider a multi-language sporting equipment store. A search for “Specialized” reveals all Specialized bicycles sold by the store, which is helpful when each language catalog sells a unique set of SKUs.
Another reason to specify search response languages explicitly is if your site supports multiple languages and you’d like to search in one, but see results in another, perhaps more familiar language. For example, a French-speaking merchandiser, who wants to see “robes” from the English catalog, but doesn’t know that in English they are called “dresses” could search for “robe” when the search text language is French and the response language is English to see dresses sold on the English-language site.
To specify response languages, you provide the languages to the Parser Options component as described in the following procedure. The procedure instructs you to create a properties file; however, if you prefer to use the ACC, select the corresponding components of class atg.search.routing.utils.Language instead of providing locales to targetLanguages.
Create a properties file for the Parser Options component with a
targetedLanguagesproperty set to a comma-separated list of languages or locales that represent the languages you want to support:$class=atg.search.routing.command.search.ParserOptions
$scope=requesttargetLanguages=en_US,en_GBSave the properties file to the local configuration directory as follows:
If you already have a Parser Options component, name this properties file for that component, and save it to the same location.
Otherwise, create a new component by naming the file anything you choose and saving to a directory, such as:
<ATG9dir>/home/localconfig/atg/commerce/searchIf you’ve created your own Parser Options component, you also need to add it to the
parserOptionsproperty of the Query Request component, which you find by checking thesearchRequestproperty of/atg/commerce/search/testing/SearchTestingQueryFormHandlerfor the name and location of the Query Request component.
For more information on the form handler class and Parser Options component, see the Search Form Handlers chapter of the ATG Search Query Guide.
