The following table lists the components of an Oracle Commerce Guided Search implementation that you must modify or create in order to support the language or languages that your application is targeting.
|
Component |
Changes required for internationalization |
For more information, see: |
|---|---|---|
|
Pre-processing scripts |
Pre-processing scripts must specify the character sets to be used by your Oracle Commerce Guided Search implementations. | |
|
Source data |
Source data must be tagged with ISO-639 codes that identify the languages in which the data is to be presented to the users of your Oracle Commerce Guided Search implementation. |
Assigning Language IDs globally, per record, and per property |
|
Language analysis |
Either Latin-1 language analysis or Oracle Language Technology (OLT) Analysis must be selected to determine how dgidx and dgraph parse and process text. | |
|
Language collations |
A suitable collation for controlling how text is sorted during indexing and query processing must be selected. | |
|
Endeca dimensions |
A separate version of each Oracle Commerce dimension must be created for each language. |
MDEX Engine Developer's Guide |
|
Oracle Commerce Guided Search indexed records |
Properties of source data records must be mapped either to dimensions or to properties of the corresponding Oracle Commerce records. |
MDEX Engine Developer's Guide |
|
Search Terms |
Search terms must be properly encoded before users of your Oracle Commerce Guided Search application submit them to a form. | |
|
Cartridge templates |
If your implementation supports multiple locales, you can localize your custom templates | |
|
Custom editors |
Create language specific custom editors for Experience Manager. | |
|
Menus |
Create language-specific menus and other aspects of the user interface that contain static text. | |
|
HTML |
Ensure that HTML pages take into account the requirements of the languages that they will display. | |
|
Text manipulation |
The following text manipulation features must be configured for use in particular languages: sorting, stemming, decompounding, thesaurus, wildcarding, spelling and did you mean, stop words, and keyword triggers. | |
|
Logging and reporting |
Consider running a separate Logserver for each language, to make it easier to run language-specific logs and reports. |
MDEX Engine Developer's Guide. |
