W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2010

Re: DOM3 key events: Editorial feedback 1

From: Doug Schepers <schepers@w3.org>
Date: Wed, 14 Apr 2010 03:00:34 -0400
Message-ID: <4BC56812.9070706@w3.org>
To: Richard Ishida <ishida@w3.org>
CC: www-dom@w3.org, public-i18n-core@w3.org
Hi, Richard-

Thanks for your helpful and detailed comments, and sorry for the delayed 
response.

I've addressed most of these in the spec, and will let you know when 
I've fixed them all.

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs



Richard Ishida wrote (on 2/17/10 7:26 AM):
> These are personal comments until such time as the i18n WG decides to endorse them.
>
> [1] 6 Note
> "Serbian and Kanji characters which are not always available (or are misrepresented) in the alternative versions or printed versions of this specification"
>
> What alternative versions?  Do you mean to say that Serbian and Kanji characters may not be visible to the reader if they don't have the right fonts installed?
>
>
> [2] 6.1.1
> "(such as 'F' or '8')"
> I would add 'or ш', ie. add a non-ASCII character as a reminder that we need to think internationally about this.
>
>
> [3] 6.1.2 etc.
>
> "it will produce 'q' ('\u0071', Latin Small Letter Q)"
>
> I believe that what you are trying to do in the parentheses is identify the character in quotes just before.  I would prefer to see the more common Unicode notation for this, ie. "it will produce 'q' (U+0041 LATIN CAPITAL LETTER Q)", and the other examples in this paragraph.
>
>
> [4] 6.1.2.2
>
> "the distribution of letters is for Western devices"
>
> Actually, as shown, this is for English devices only.
>
>
> [5] 6.2
>
> I think some mention of textInput and it's relationship to key values would be helpful here.  Cf. 5.2.6 which says "It is therefore highly recommended to rely on Text events types when dealing with character input".
>
>
>
> [6] 6.2.2
>
> "The following example describes a possible sequence of keys to generate the Unicode character Q"
>
> I think that, and a number of later sentences in the document, should say:
>
> "The following example describes a possible sequence of events associated with the generation of the Unicode character Q"
>
> I also think it would be clearer to make these lists into tables with headings:
>
> Event		Returned value		Keys involved
>
> and to use more descriptive text for the latter.
>
>
> [7] 6.2.1
>
> "The character values in the key values set are derived from the popular Unicode standard [Unicode], and as such, have certain advantages."
>
>>>
>
> "The character values in the key values set are Unicode [Unicode] code points, and as such, have certain advantages."
>
>
> [8] 6.2.6
>
> "Here is a algorithm"
>
>>>
>
> "Here is an algorithm"
>
>
> [9] 6.2.3, first example
>
> The example uses eacute é where it should use ecircumflex ê.
>
>
>
>
> I have more editorial comments, but will await a response to my previous mail before sending.
>
> Hope that helps,
>
> RI
>
>
>
>
> ============
> Richard Ishida
> Internationalization Lead
> W3C (World Wide Web Consortium)
>
> http://www.w3.org/International/
> http://rishida.net/
>
>
>
>
Received on Wednesday, 14 April 2010 07:00:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:04 GMT