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 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:04 GMT