- From: Daniel Glazman <daniel.glazman@libertysurf.fr>
- Date: Fri, 10 Mar 2000 03:58:21 +0100
- To: Bert Bos <Bert.Bos@sophia.inria.fr>
- CC: Yung-Fong Tang <ftang@netscape.com>, Erik van der Poel <erik@netscape.com>, www-style@w3.org, mozilla-i18n@mozilla.org, pierre@netscape.com, tao@netscape.com, bobj@netscape.com
Bert Bos a écrit :
>
> Was this ever brought to a conclusion? I missed the thread at the time
> and only just noticed it.
>
> I believe the answer is in two parts:
>
> 1 For a local file there is no default. If the filesystem provides
> out-of-band metadata, you can use that, otherwise you're on your
> own.
>
> 2 On the wire, the specifications of MIME and HTTP govern the
> default. The default in MIME for all text/* types is US-ASCII.
> In HTTP the default is ISO-8859-1.
>
> That leaves FTP and other protocols undefined, of course, but I'm not
> sure that's our responsability.
>
> [snip]
>
> > > My opinion is that it is reasonable to default to whatever charset has
> > > been set in the user's menu, which might be an auto-detector.
Exactly. I don't really think we need more than the contents of the
section 4.4 of CSS 2 spec :
<BLOCKQUOTE>
When a style sheet resides in a separate file, user agents must observe
the following priorities when determining a document's character encoding
(from highest priority to lowest):
1. An HTTP "charset" parameter in a "Content-Type" field.
2. The @charset at-rule.
3. Mechanisms of the language of the referencing document (e.g., in
HTML, the "charset" attribute of the LINK element).
</BLOCKQUOTE>
If you consider that the user's choice is a user @charset at-rule defined
in a user stylesheet overriding HTTP charset and existing @charset in a
downloaded stylesheet, you have everything you need, don't you ?
</Daniel>
--
PS : Salut pierre@netscape ! comme on se retrouve :-)
Received on Thursday, 9 March 2000 22:00:04 UTC