W3C home > Mailing lists > Public > public-xhtml2@w3.org > May 2008

Re: Document Character Set, UNICODE, xhtml-access, and @key

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Wed, 21 May 2008 15:32:35 +0200
To: "Shane McCarron" <shane@aptest.com>, "XHTML WG" <public-xhtml2@w3.org>
Message-ID: <op.ubiakledsmjzpq@acer3010>

On Tue, 20 May 2008 00:54:35 +0200, Shane McCarron <shane@aptest.com>  
wrote:

> So..... What does this mean for us.  I think it means we are saying an  
> @key value is an ISO 10646 character from the 'Char' production of XML.   
> And that a user agent needs to map that into its local processing  
> (document character set) before registering an event handler that maps  
> the key to some event (change focus, actuate or not).  Moreover, I think  
> that @key is explicitly NOT a character from the document character  
> set.  But.... I am not an expert in this area, and I could be wrong.  If  
> there really is an issue here (as Tina and I suspect there is) I think  
> we can just submit it as a last call comment against our own document.   
> This is pretty subtle.

Correct me if I am wrong, but the document character set is always ISO  
10646 in XML (and modern HTML). So the only mapping that needs to be done  
is the standard mapping from the character encoding as the document comes  
in to ISO 10646.

Or do I misunderstand your question?

Steven
Received on Wednesday, 21 May 2008 13:33:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 February 2010 18:12:48 GMT