W3C home > Mailing lists > Public > www-international@w3.org > October to December 1997

Re: Unnecessary redraws with Content-Language

From: Chris Wendt <christw@microsoft.com>
Date: Fri, 14 Nov 1997 11:15:58 -0800
Message-ID: <03d801bcf131$bceafea0$8b53369d@christw3.dns.microsoft.com>
To: <erik@netscape.com>, "Reinier van Kleij" <rklei@acm.org>
Cc: <www-international@w3.org>
Confirming what Erik says:

We _have_ to reload, reconvert to the target charset and re-render the
document on encountering the <meta.... charset=...> tag if the indicated
charset differs from what we expected, typically the current user default of
the browser.

The effect can be minimized by either sending the charset in the http header
or moving the <meta ... charset=...> close to the top of the document. I
usually recommend as first statement in the <head>.

Chris..

-----Original Message-----
From: Erik van der Poel <erik@netscape.com>
To: Reinier van Kleij <rklei@acm.org>
Cc: www-international@w3.org <www-international@w3.org>
Date: Friday, November 14, 1997 10:08 AM
Subject: Re: Unnecessary redraws with Content-Language


>You are probably referring to the charset parameter:
>
><meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
>
>Netscape's client will redraw the document if it encounters a charset
parameter
>that is different from what it had been assuming until then (i.e. the View
|
>Encoding menu setting).
>
>Erik
>
>Reinier van Kleij wrote:
>
>> we have been testing some of the META elements for internationalisation
>> purposes. We suspect that the Content-Language tag causes unnecessary
>> redraws of the page by various browsers (Netscape and IE): the page is
>> first downloaded and rendered according to the default language and then
it
>> is redrawn to render it correctly for the language indicated by the
>> Content-Language tag.
Received on Friday, 14 November 1997 14:17:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:48 GMT