Article ID: 843522 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
This article describes an update to the Search HTML filter in Microsoft Office SharePoint Portal Server 2003. When you use this update, you can configure the code page that is used to filter HTML documents.
By default, the Search HTML Filter in SharePoint Portal Server 2003 uses a Unicode Transmission Format-8 (UTF-8) code page as the default code page. If an HTML document does not specify a character set to use, the Search HTML filter uses a UTF-8 code page to filter the document properties of the HTML document. This behavior differs from the behavior of Microsoft SharePoint Portal Server 2001. The Search HTML filter in SharePoint Portal Server 2001 uses a code page that is based on the locale of the server. You can use the update to configure the Search HTML filter to use a code page that is based on the locale of the server.
This problem is corrected in Microsoft Office SharePoint Portal Server 2003 Service Pack 2.
To resolve this problem, obtain the latest service pack for SharePoint Portal Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889380After you install the service pack, follow the steps that are listed in the "More Information" section to set the HTMLFiltUseLocaleForDefaultCodePage registry entry and to enable the hotfix.
(http://support.microsoft.com/kb/889380/ )How to obtain the latest service pack for SharePoint Portal Server 2003
You may want to configure the Search HTML filter to use a code page that is based on the locale of the server when you want SharePoint Portal Server 2003 to use the same behavior as SharePoint Portal Server 2001. For example, you click Item Details to view the details of an HTML document that is returned in the search results. You notice that the values of certain properties of the document are displayed incorrectly. The HTML document contains high ASCII characters that use ANSI encoding.
In this scenario, configure the Search HTML filter in SharePoint Portal Server 2003 to use a code page that is based on the locale of the server so that the HTML document is filtered correctly. To do this, obtain the hotfix, and then follow the steps in the "Add the HTMLFiltUseLocaleForDefaultCodePage registry entry after you install the hotfix" section.
How to obtain the hotfixThis issue is fixed in the SharePoint Portal Server 2003 post-Service Pack 1 Hotfix Package that is dated September 17, 2004. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/883919/ )Description of the Office SharePoint Portal Server 2003 post-Service Pack 1 Hotfix Package: September 17, 2004
Add the HTMLFiltUseLocaleForDefaultCodePage registry entry after you install the hotfixAfter you install this hotfix, add the HTMLFiltUseLocaleForDefaultCodePage registry entry to the following registry subkey, and then set the registry entry to either 1 or 0 (zero), depending on your situation:
The following describes the values that you can use for the HTMLFiltUseLocaleForDefaultCodePage registry entry:
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
For more information about SharePoint Portal Server 2003, visit the following Microsoft Web site:
Article ID: 843522 - Last Review: April 24, 2007 - Revision: 2.6
Contact us for more help