- From: Erik van der Poel <erik@netscape.com>
- Date: Tue, 18 Nov 1997 11:33:44 -0800
- To: Reinier van Kleij <rklei@acm.org>
- CC: Chris Wendt <christw@microsoft.com>, www-international@w3.org
Reinier van Kleij wrote: > actually we have: > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> > <HTML> > <HEAD> > > <META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=iso-8859-1"> > <META HTTP-EQUIV="Content-Language" CONTENT="it"> > > So according to you, we can not do any better: the Content-Type right after > <HEAD>? You can do "better": use the HTTP Content-Type header's charset parameter. I don't know which server you are using, but you probably need to "tell" it to use the right Content-Type header. Netscape doesn't do anything with Content-Language (yet). > Netscape and IE seem to do these redraws still, so maybe Netscape/IE draw > the page, then check the character set and decide to redraw? Are you sure that the redraw is due to the charset? Have you tried it with and without the charset? Erik
Received on Tuesday, 18 November 1997 14:34:08 UTC