Novell NETWARE 6-DOCUMENTATION Manual page 2147

HTML Encodings
218 Getting Results with Novell Web Services
page. Other characters can still be sent to the Web Search services using the
%uHHHH and %HH formats, but the browser will not allow users to enter
normal text characters other than that supported by iso-8859-1.
Although Web Search can return search results from many languages, some
characters found in titles and descriptions might be returned as question marks
(?) indicating that these characters are not available in the current response
encoding. If a character can be represented in the current encoding but a font
is not available, many browsers will substitute an alternate character such as
an empty box character. Once the appropriate fonts have been installed, these
characters will then display properly.
By default, NetWare Web Search returns all search, print, and administration
pages in UTF-8.
Since HTML content can contain text written in many character sets, all
HTML files need to include a tag that identifies the character set encoding. To
identify the encoding of an HTML file (or search template), use the following
META tag at the top of the file's header section:
<meta http-equiv="Content-Type" content="text/html;
charset=Shift_JIS">
In this example, you would replace Shift_JIS with the appropriate Internet
Assigned Numbers Authority (IANA)-assigned encoding value.
It is very important that the CHARSET value accurately represent the
character set encoding that was actually used when the HTML Web content or
Web Search template was created. A correct entry allows Web Search to
accurately interpret and convert the characters in the document. An incorrect
entry prevents Web Search from being able to read the characters as valid data
in the authored language.
IMPORTANT:
Improperly identified characters result in garbled text. In some
cases, the Web-based content cannot be properly indexed or printed. In the most
severe cases, the document being read might produce a server-side exception,
which will ultimately discontinue processing the document and perhaps the entire
current operation.
Because Web Search is Unicode-based, when reading templates or when
indexing or printing HTML content, all character encodings are converted
from their source encoding to Unicode for internal processing.