W3C home > Mailing lists > Public > www-html-editor@w3.org > October to December 2008

Re: [XHTMLAccess] i18n comment 2: Keycode or character

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Wed, 26 Nov 2008 15:46:16 +0100
To: ishida@w3.org, www-html-editor@w3.org, public-i18n-core@w3.org
Message-ID: <op.uk8dzeoesmjzpq@acer3010.ins.cwi.nl>

Thanks.

We have tried to address this by making certain that people understand  
that "key" is
   an abstraction and does not correlate to a "key code".

Please see the latest editor's draft for full details.
http://www.w3.org/MarkUp/2008/ED-xhtml-access-20081023/

Best wishes,

Steven Pemberton


On Wed, 06 Aug 2008 09:12:28 +0200, <ishida@w3.org> wrote:

>
> Comment from the i18n review of:
> http://www.w3.org/MarkUp/2008/WD-xhtml-access-20080526/
>
> Comment 2
> At  
> http://www.w3.org/International/reviews/0806-xhtml-access/Overview.html
> Editorial/substantive: S
> Tracked by: RI
>
> Location in reviewed document:
> 3.1.2  
> [http://www.w3.org/MarkUp/2008/WD-xhtml-access-20080526/#sec_3.1.2.]
>
> Comment:
> It isn't clear that this section has taken into account the potential  
> difference between key codes and the characters that may result from a  
> key press on a given keyboard. It seems to assume that the character on  
> a key cap == the key code identifier == the character produced by  
> pressing that key == the character that is the value of the key  
> attribute.
>
> This is not always the case when you take into account a variety of  
> keyboards serving various different locales.
>
> Please provide some precision as to how a key attribute value is  
> associated with keyboard events. (Note that this has proved to be a  
> difficult topic for the specification of DOM3 keyboard events.)
>
>
>
Received on Wednesday, 26 November 2008 14:46:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:17:59 GMT