In his this article you’ll find:

Goal

This article aims to give an overview of the multilingual indexing functionality, to explain the main specifics and what the benefits of using it are. It will explain when it is appropriate to use this functionality and what is the expected behaviour when using it.

Overview

Multilingual is a feature that Hawksearch provides to make searching and finding information in multilingual environments more convenient and systematic. Most platforms have the option to change the language and translate the articles to reach a larger audience. This is something that also happens with the help of Kentico, where we can translate and develop content in different languages. This has led to the need for the connector to allow its users to filter and group their content according to the languages in which it is created.

Specifics of multilingual functionality

Indexing

Indexing API

When indexing with the multilingual functionality enabled, the connector will add another field to each document called “language” which will include the culture code for that specific document.

File Export

The file export doesn’t perform that conversion out of the box, but you can add an attribute called “language” that gets its value from the “DocumentCulture” column from the database. That information is stored in the CMS_Document database table.

Searching

The results the user sees when the page is loaded are the ones from the Default culture. If English is the default one then loading the page will show results in English. Changing the default language will also change the results that appear when the results page loads.

Which language is selected can be easily distinguished from the page URL. You can see a language query parameter with the currently selected culture code. For example “http://localhost/home?language=en-us“.

The advantages of multilingual functionality

• Makes the searching easier

• Gives another option to filter the results

• Allows for more accurate targeting. For example, if the results are in German, one type of product should be published as a priority, and those in English as a secondary