W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: Comments on Last Call Working Draft of XHR

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 16 Dec 2009 15:57:53 +0100
To: "Richard Ishida" <ishida@w3.org>, "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.u41c6ryt64w2qv@annevk-t60>
On Thu, 26 Nov 2009 18:25:57 +0100, Richard Ishida <ishida@w3.org> wrote:
> Hopefully you'll get a formal response from the i18n WG shortly.  In the  
> meantime, I have only a couple of personal editorial suggestions:

I have not seen a response from the i18n WG.


> [1] 2.2 terminology
> It would help a lot to link each of the terms defined in html5 to the  
> appropriate location in the html5 spec, if possible.

We have this situation in several specifications at the moment. I'm not  
sure what the correct solution will be here so I rather wait with  
implementing something until we agree on something that will work  
everywhere. I agree it is not ideal, but having to update all the  
terminology links all the time is not great either.


> [2] same section
>
> I was confused by the term "document's character encoding".  I suspect  
> this ought to be "character encoding (of the document)", where the  
> parenthesised text is non-bold.  The problem was that I thought  
> "document's character encoding" was a single term, like "URL character  
> encoding", and was something different than "character encoding" (in the  
> same way that "document character set" is different from "character  
> set").

It is actually a single term, defined by HTML5.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Wednesday, 16 December 2009 14:58:32 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT