doug: how do i get the character
I want when I press a (sequence) of buttons?
... such as dead keys (Option-U + o == ö
... or perhaps Shift-Q => Q
... or third case, IME
... (transformation, choose from lists and such)
... problem #2
... you write a game, for example, and want 'a', 's','d', 'w'
be arrow keys
... or you want Ctrl-C to be your copy function
... even if 'c' is remapped to 'h'
... the physical layout is the same
... this is not in the scope of dom3 events

addison: so problem 2 is
detecting a physical key press on physical keyboard

richard: so access keys are not
included?

doug: never been part of it
... but for example XHTML2 Access... for accesskey
... handwaves over the problem of keys
... rewrote that document and hoping to get published in terms
of key identifiers
... solved problem #1
... broke it down
... want single token to id each key
... don't believe that a single id can be had for each
key
... key id mechanism can produce similar results across
operating systems
... if i have a US-QWERTY keyboard...
... and press 'q'
... when I get 'Q'
... as keycode
... further level of abstraction from java/.net
... if the key produces a character
... then that's key id
... some keys can have more than one identifier
... text input event might give you same value as key id
... if you paste in text or are using IME
... those come as text input events
... also something new...
... composition events
... start, update, end
... implemented in FF
... to enable on-the-spot editing

richard: once you get key id then
you do someting with it
... so that's where an access key or accelerator might come
in
... so when typing in japanese
... the ime captures qwerty keys and converts to hiragana for
example
... but when you have an accelerator key, like, say 'k'
... you don't want to interpret as hiragana first

doug: some things to watch out
for
... list of key ids
... will change in next draft
... some have one value, some have 2, or 3
... some different colors
... for whatever reason, syntax is U+####

(U+20AC"

<r12a> 'j'

<r12a> 'U+006A'

<r12a> The Latin Miniscule
Letter j key.

doug: problem I wish to
solve
... see if character typed was in a certain range
... meaning block, script, etc.
... such as \p{Greek}
... want to say regex "is this in a range I want"
... rather than U+

doug: added util method to DOM3
events
... converts to some format
... entity, name, or U+ representation, or a character
... for some characters, for example 'j'
... or its Unicode code point string

<r12a> j U+006A: LATIN SMALL
LETTER J

addison: use Unicode names for
characters

doug: so some people "hey, do we
need conversion"?
... propose instead of U+
... use \u string

supplementary planes

addison: the characters on those
planes are real and keyable
... example: emoji
... or Chinese characters on plane 2

doug: we need to hear this
feedback
... need even one specific example
... please send in a comment saying "this is a real world use
case"
... will point to thread
... is there utility in tranformational utility

addison: could see use for
normalizer of char names
... and key ids

doug: so now: key ids can be 'j'
or 'U+006A'
... but plan to collapse to '\u006a'

<r12a> 𐎄

<r12a> U+10384

(see cuneiform character)

<r12a> \uD800\uDF84

<r12a> \U00010384

C version has fixed length

<r12a> &#x10384;

vs. &#x6a;

<r12a> shepazu requests:

<r12a> explain why it would
be better not to use the javascript escapes for supplementary
characters