W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

Re: [review feedback] qa-css-charset

From: Richard Ishida <ishida@w3.org>
Date: Tue, 18 Mar 2014 12:45:00 +0000
Message-ID: <53283FCC.1070703@w3.org>
To: Gunnar Bittersmann <gunnar@bittersmann.de>, www-international@w3.org
On 18/03/2014 08:51, Gunnar Bittersmann wrote:
> Richard Ishida scripsit (2014-03-17 18:00+01:00):
>> I have taken these comments and those in the previous two emails into
>> account in the latest version of the article.
> What about my mail from 2014-03-12 17:19Z?
> »»
> If your HTML and CSS files use the same non-UTF-8 encoding, the latest
> versions of major browsers will apply the encoding of the HTML file to
> the CSS stylesheet.
> ««
> This sounds as if this browser behavior differs for UTF-8 while in fact
> is the same. Add ‘also’ (‘will also apply’) or delete ‘non-UTF-8’ (‘use
> the same encoding’).

Removed 'non-UTF-8'.

> »»
> You can also override any server defaults or declare the encoding of the
> file in the HTTP Content-Type header if you have access to the server
> settings or use server-side scripts
> ««
> ‘or’? Make it ‘to declare’ or remove ‘or declare the encoding of the
> file in the HTTP Content-Type header’

I tried to make this clearer by removing that sentence and adding the 
following after the figure:

"It could be that the server is serving a style sheet with an encoding 
declaration that you don't want, due to server-wide defaults or specific 
settings, or serving without an encoding declaration when you want one. 
You can change change the situation either for the server as a whole, or 
for a specific file or set of files, by changing the server settings 
(globally or locally) or by using code in scripts such as PHP."

> Elements of class "sideinfonote" are somtimes div, other times aside.



> Cheers,
> Gunnar
Received on Tuesday, 18 March 2014 12:45:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:04 UTC