W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2008

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

From: Phillips, Addison <addison@amazon.com>
Date: Wed, 26 Nov 2008 07:28:18 -0800
To: Steven Pemberton <steven.pemberton@cwi.nl>, "ishida@w3.org" <ishida@w3.org>, "www-html-editor@w3.org" <www-html-editor@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA017B35430F@EX-SEA5-D.ant.amazon.com>
(personal response)

I think this text moves in the right direction, but think that there may still be problems with it. Mainly, I think it is now unclear how the 'key' attribute is supposed to work, given that the word key is both disclaimed and also used to mean (or at least imply) actual keypresses.

It should be noted that there is not a well-defined solution to this problem. WebAPI has been struggling with this also. In practice, how physical key events and character input are related is normally handled at a fairly low level in the system. Higher level software that attempts to listen and respond to key press events often ends up damaging or disabling more complex input systems, such as the IMEs (input method editors) used to compose e.g. East Asian text.

(chair hat ON)

Thanks for the response. The I18N WG will review your response and text in detail. Our next teleconference is today.

Addison

Addison Phillips
Globalization Architect -- Lab126
Chair -- W3C Internationalization Core WG

Internationalization is not a feature.
It is an architecture.


> -----Original Message-----
> From: public-i18n-core-request@w3.org [mailto:public-i18n-core-
> request@w3.org] On Behalf Of Steven Pemberton
> Sent: Wednesday, November 26, 2008 6:46 AM
> To: ishida@w3.org; www-html-editor@w3.org; public-i18n-core@w3.org
> Subject: Re: [XHTMLAccess] i18n comment 2: Keycode or character
> 
> 
> 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 15:29:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 26 November 2008 15:29:01 GMT