> On Mon, 8 Jun 1998, Otto Stolz wrote:
> > Netscape Communicator 4.05 (for X-Windows/Unix) apparently does not,
> > though the page contains the tag
> > <meta http-equiv="Content-Type" content="text/html; charset=UTF
> > I have to manually change the setting in the View/Encoding menu to
> > "Unicode (UTF-8)", otherwise the browser will assume Latin-1 encoding.
> It is a chicken-egg problem when the encoding is encoded in the
> file. I've found reloading the page usually works when Netscape
> gets it wrong the first time around.
> It is much better to configure the server to send out proper HTTP
I have never had a problem with the above syntax providing
the file was served by our Web server. It did not work
if I tried pointing directly to the file, bypassing the
Web server. That is, with the file: protocol, the META
tag is ignored.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:40 EDT