Frank Tang
from the
Netscape Team tell me
about their plans of implementing Accept-Charset field
into after-3.0 releases, but it seems they forget it,
if you'll ask them too,
it can be faster.
Netscape client must put acceptable charset (KOI8-R assumed) via
Accept-Charset header
field when interact with HTTPD, but not do it currently.
Frank Tang
from the
Netscape Team tell me
about their plans of implementing Accept-Charset field
into after-3.0 releases, but it seems they forget it,
if you'll ask them too,
it can be faster.
You need to fix font header via any .TTF font editor (f.e. Font Monster): change Proportion from Any to Monospaced (fixed-pitch flag CF_FIXEDPITCHONLY from the CHOOSEFONT structure) and change Family Type from Decorative to Text/Display, if neccessary.
See also Win3.* Netscape tuning, X11 Netscape tuning.
Additional links: Cyrillic for MS Windows Netscape, Netscape Internationalization Secrets.
|