Re: Two new encoding related articles for review

I believe I have done all these things.
Thanks.
RI


On 08/03/2014 05:16, Gunnar Bittersmann wrote:
> »»
> $status = 'draft'
> ««
>
> Should be set to 'review' for both articles now.
>
> In text, you might want to use ’ U+2019 for apostrophes and “ U+201C / ”
> U+201D or ‘ U+2018 / ’ U+2019 respectively for quotations (also in
> http://www.w3.org/International/questions/qa-html-encoding-declarations-new).
>
>
>
>> Choosing & applying a character encoding
>> http://www.w3.org/International/questions/qa-choosing-encodings-new
>
> »»
> described in Declaring character encodings in HTML.
> ««
> »»
> see Normalization in HTML and CSS. For information about the 'Unicode
> Signature (BOM)', see The byte-order mark (BOM) in HTML.
> ««
> »»
> in the article Migrating to Unicode.
> ««
>
> Article titles should be set in italics, i.e. wrapped in cite elements.
>
>
> »»
> Any character encoding declaration in the HTTP headers will override
> declarations inside the page.
> ««
>
> Use singular: in the HTTP header (one page – one header)
>
> »»
> You should also avoid the replacement encoding.
> ««
>
> What is that? I don’t think the term is clear to the reader.
>
>
>> Declaring character encodings in CSS
>> http://www.w3.org/International/questions/qa-css-charset-new
>
> »»
> in selector values
> ««
>
> Is there such thing as “selector value”? Better: “in selector names”? Or
> just “in selectors”.
>
>
> »»
> In this case you should use @charset, or HTTP headers
> ««
>
> Remove comma: @charset or HTTP headers
>
>
> Gun*nitpicker*nar
>
>

Received on Monday, 10 March 2014 11:07:48 UTC