|
WARNING: This method is only workaround for those of you who can't instruct your HTTPD daemon and should be avoided when possible. Although this method is standard and should be understanded by all related soft, it can cause additional troubles for proxy or intelligent cache. Much better variant is Method which requires HTTP daemon actions, but it can be not available in some cases (f.e. if you have several foreign mirrors of your page).
You need to
insert into the <HEAD> section of your document
the following statement (as early as possible):
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=KOI8-R">
This method assumes that your browser understands
<META HTTP-EQUIV="Content-Type ... charset=name">
tag as described in
Internationalization of the Hypertext Markup Language (RFC 2070)
(f.e. Netscape or
Internet Explorer does).
Your browser needs to know about
KOI8-R chararter set itself too, of course.
The documents have fixed
chararter set in this case and no on-the-fly document encoding conversion
is possible.
To check if your browser support this method, set its default encoding
to ISO8859-1 or Western and try to load any page with KOI8-R
image ALT= tag,
then you'll see
Russian text if this method supported or some cryptic text in
ISO8859-1 if not supported.
|
|