Extended Characters Must Be Encoded in UTF-8 or UTF-16 (319200)


The information in this article applies to:

  • Microsoft TV Server
This article was previously published under Q319200

SYMPTOMS

The Centers tool and the Search tool cannot display content information that contains extended characters (such as the umlaut character).

CAUSE

TV Server only supports XML partner pulls in standard ASCII and UTF-8 and UTF-16 encodings.

WORKAROUND

If you want to include extended characters in the content, use standard XML encoding schemes so that these extended characters must be converted to either the UTF-8 or UTF-16 format. The XML parser does not require all encodings except UTF-8 (which explains ASCII) and UTF-16.

STATUS

This behavior is by design.

MORE INFORMATION

TV Server uses the XML DOM that is a standard component in Microsoft Windows 2000. Although the XML DOM in Windows 2000 supports Unicode (even though it is not required), the TV Server 1.0 programs do not support Unicode XML Partner Pull.

NOTE: All of the XML parsers must support UTF-8 and UTF-16, and other encodings are not required. To determine if the MSXML parser supports an encoding format, type the encoding in the header of an XML file, and then open the file in the browser. For example, type the following sample code in the header of an XML file: 
<?xml version="1.0" encoding="ANSI"?>
When you open the file in the browser, you receive the following error message:
"System does not support the specified encoding"
TV Server programs support UTF-8 and ASCII, and these programs do not support standard Unicode.

There are multiple ways to handle "extended" characters. Note that to send information that uses extended characters, use UTF-8 or UTF-16 for the XML feed.
Modification Type:MinorLast Reviewed:6/18/2003
Keywords:kbenv kberrmsg kbpending kbprb kbui KB319200
©2003 Microsoft Corporation. All rights reserved.