RE: Key Events internationalization

Hi Björn,

> -----Original Message-----
> From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net] 
> Sent: 29 August 2007 21:22
> To: Richard Ishida
> Cc: public-webapi@w3.org; public-i18n-core@w3.org
> Subject: Re: Key Events internationalization
> 
> * Richard Ishida wrote:
> >The DOM appendix A gives an example of pressing the key 
> engraved with Q 
> >on a US physical kbd with a serbian mapping applied.  The example 
> >quotes the result as "keydown": "U+0409".  How is the implementation 
> >supposed to figure out that the appropriate identifier is 
> U+0409, when 
> >all the tests I've done have returned the 81 (Q) result.
> 
> Your application is looking at the .keyCode and .charCode 
> attributes; 

Yes. 

> those have yet to be specified and they are not 
> part of the appendix.

Oh.  So there is a plan to specify those? If so, how would they differ from
the .keyIdentifier, and what is .keyIdentifier for?


> Instead the appendix discusses the .keyIdentifier attribute.

So were/how does the .keyIdentifier attribute get its information?


> 
> >Does the implementation have tables for every keyboard mapping and 
> >every physical keyboard, and use those to map the codes 
> coming from the 
> >keyboard into the right identifier?
> 
> I am not sure why an implementation of DOM Level 3 Events 
> would, it seems to me the keyboard mapping happens at a lower 
> level. Could you perhaps rephrase the question?

See last the question above.

RI