Configuring Index Server to Use the Neutral Word Breaker
ID: Q246701
|
The information in this article applies to:
-
Microsoft Index Server version 2.0
SUMMARY
Some searches against Microsoft Index Server may fail when using a language specific word breaker. he Neutral word breaker can be used as a workaround. This article explains removing the language specific word breaker ensuring that the Neutral word breaker is used.
MORE INFORMATION
IMPORTANT: This article contains information about editing the registry.
Before you edit the registry, make sure you understand how to restore it if
a problem occurs. For information about how to do this, view the "Restoring
the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help
topic in Regedt32.exe.
WARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry Editor
can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys and
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should back up the registry before you edit it.
If you are running Windows NT, you should also update your Emergency
Repair Disk (ERD).
The following is an example on how to remove all word breakers except for the Neutral word breaker
- Run Regedt32.exe.
- Select:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ContentIndex\Language
- Select the Language key and Save it to a backup file.
- Double-click on the InstalledLangs value and remove all lines except for the one showing "Neutral". Click OK.
- Delete all keys except Neutral below Language.
- Stop and then restart the index service.
- Rebuild the catalog by doing a full build.
There are some differences that should be noted when using only the Neutral word breaker:
- In all languages, "advanced" normalization acts differently:
- Dates: 9/9/99 and 9-9-1999 will not match
- Numbers: 1,000 and 1000 will not match
- Hyphens: database and data-base will not match
- In German compound decomposition will not work.
- In other European languages lose clitic stripping is lost, which may reduce the chances of matching.
- Word stemming will no longer work. Word stemming is where a query on "flew**" returns documents matching flew, fly, flown, and so forth.
Additional query words:
Keywords : kbDSupport
Version : winnt:2.0
Platform : winnt
Issue type : kbinfo