Title: How to customise the paths used by Stemming Language Selector 2 (configuration file)

Ref: ED105
Last updated: 15-Aug-2007

 

There are two ways to do this:

a) By editing the short-cut properties (i.e. add command-line switches) See this article

b) By editing the configuration file as shown below.

Step 1. In Windows Explorer navigate to the folder where you have installed the Stemming Selector 2 application

Step 2. Open the CONFIG file (StemSelect.exe.config) in Notepad or a suitable XML editor.

Step 3. Locate this section:

</userSettings>

<applicationSettings>

<StemSelect.My.MySettings>

<setting name="SourceStemPath" serializeAs="String">

<value />

</setting>

<setting name="TargetStemPath" serializeAs="String">

<value />

</setting>

</StemSelect.My.MySettings>

</applicationSettings>

Step 4. Edit the paths where the stemming files are located (SourceStemPath) and where the dtSearch Engine
expects to find the stemming.dat file (TargetStemPath) in the <value> </value> section.

Example:

<setting name="SourceStemPath" serializeAs="String">

<value> “C:\Program Files\dtSearch\Language\Stemming” </value>

</setting>

<setting name="TargetStemPath" serializeAs="String">

<value>“C:\Program Files\dtSearch\bin" </value>

This example shows the normal paths as used in a default dtSearch Desktop installation, but you can
choose paths anywhere on the same machine.

Paths must be enclosed in quotation marks as shown.

The user must have read\write permissions for the TargetStemPath and read permission for the SourceStemPath.

Step 5. Save the file, make sure you save the file in utf-8 format.

IMPORTANT

Any command-line arguments passed to StemSelect.exe will override the settings in the configuration file, this enables the
customer to override either or both of these paths without having to edit the XML file.

To troubleshoot problems with command-line arguments or configuration settings create a debug log, this will show the way the
Stemming Language Selector application interprets the values supplied. See this article for details of how to prepare a debug log.