W3C home > Mailing lists > Public > www-international@w3.org > July to September 2010

RE: For review: 6 new and 2 updated articles about character encoding

From: Richard Ishida <ishida@w3.org>
Date: Wed, 25 Aug 2010 19:16:35 +0100
To: "'Gunnar Bittersmann'" <gunnar@bittersmann.de>
Cc: <www-international@w3.org>
Message-ID: <024e01cb4481$a782d3b0$f6887b10$@org>
From: www-international-request@w3.org [mailto:www-international-
> request@w3.org] On Behalf Of Gunnar Bittersmann
> Sent: 18 August 2010 17:37
> To: www-international@w3.org
> Subject: Re: For review: 6 new and 2 updated articles about character
> encoding
> 
> I finally got through the last two of the articles, so here we go.
> 
> http://www.w3.org/International/questions/qa-html-encoding-
> declarations.en.php#quick
> under XHTML 1.x served as XML:
> 
> despite the already reported encoding pseudo-attribute:
> 
> “Ensure there is nothing before it, including spaces.”
> 
> Hm, a BOM might occur befor the XML declaration. Should that be
> mentioned in that place?

I hesitated on that, but since you mentioned it, I added something.

> 
> There’s a '?' missing in the XML declaration, make it:
> <?xml version="1.0" encoding="UTF-8"?>

Fixed.

> 
> 
> http://www.w3.org/International/questions/qa-html-encoding-
> declarations.en.php#httpheadwhat
> under Disadvantages:
> 
> “…on the server - especially when dealing…”
> 
> Use a dash, not a hyphen: on the server – especially when dealing

Done.

> 
> http://www.w3.org/International/questions/qa-html-encoding-
> declarations.en.php#xmldeclaration
> under Using the XML declaration for XHTML served as HTML:
> 
> “This would make the top of the above file look like this:”
> 
> This is confusing to me. What above file? That one that was encoded in
> UTF-8?
> 
> Proposal: This would make the top of a file look like this:

Done.

> 
> In the code example:
> 
> Capitalize ISO-8859-1 (for consistency reasons). It is in capitals in
> the next code example in the article and in the IANA registry.

Hmm. Ok then.

> Close the 'meta' element with '/>':
> <meta http-equiv="Content-type" content="text/html;charset=iso-8859-1"/>

Done.

> ***
> 
> http://www.w3.org/International/questions/qa-choosing-encodings#avoid
> 
> “Documents should not use UTF-32, […]
> The specification also advises against the use of UTF-32.”
> 
> Duplicate content.

Fixed.

> 
> 
> I somehow miss the advice against a BOM in UTF-8. (The Dreamweaver
> screenshot even shows the option “Include Unicode Signature (BOM)”.) Is
> it out of the scope of this article?

Yes.  This is just about choosing an encoding.  Bom stuff is about declaring it.

Thanks for your careful review!
RI
Received on Wednesday, 25 August 2010 18:17:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 August 2010 18:17:10 GMT