-i18n-c...@w3.org
Cc: XHTML WG
Subject: Re: [XHTMLAccess] i18n comment 2: Keycode or character
Hello Addison,
We discussed this at a recent call, and came to the conclusion was
that
the mismatch here was caused by the choice of the attribute key.
We only
chose this name because it was close
, 2009 7:40 AM
To: Steven Pemberton; Phillips, Addison; ish...@w3.org; www-html-
edi...@w3.org; public-i18n-c...@w3.org
Cc: XHTML WG
Subject: [ACTION-47] Re: [XHTMLAccess] i18n comment 2: Keycode or
character
Hi Addison,
We would really like to move forward on this.
So are you OK
Pemberton; ish...@w3.org; www-html-editor@w3.org;
public-i18n-c...@w3.org
Subject: RE: [XHTMLAccess] i18n comment 2: Keycode or character
(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
; Steven Pemberton; ish...@w3.org; www-html-
edi...@w3.org; public-i18n-c...@w3.org
Subject: RE: [XHTMLAccess] i18n comment 2: Keycode or character
Hi Steven and HTML WG,
This note is on behalf of the Internationalization Core WG.
We recently received your responses to our comments
I don't understand the meaning of characters from the document character
set
--
Ori Idan
On Wed, Nov 26, 2008 at 4:46 PM, Steven Pemberton
[EMAIL PROTECTED]wrote:
Thanks.
We have tried to address this by making certain that people understand that
key is
an abstraction and does not
