Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-06-03 Thread Ian Hickson
On Sat, 4 Apr 2009, Innovimax SARL wrote:
 
 In 2.3 Case-sensitivity and string comparison
 
 Please replace
 
 Converting a string to uppercase
 and
 Converting a string to lowercase
 
 by respectively
 
 Converting a string to uppercase ASCII
 and
 Converting a string to lowercase ASCII

Done.

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'


Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-06-03 Thread Innovimax SARL
Thanks, Ian !

On Wed, Jun 3, 2009 at 8:45 AM, Ian Hickson i...@hixie.ch wrote:

 On Sat, 4 Apr 2009, Innovimax SARL wrote:
 
  In 2.3 Case-sensitivity and string comparison
 
  Please replace
 
  Converting a string to uppercase
  and
  Converting a string to lowercase
 
  by respectively
 
  Converting a string to uppercase ASCII
  and
  Converting a string to lowercase ASCII

 Done.

 --
 Ian Hickson   U+1047E)\._.,--,'``.fL
 http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
 Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'




-- 
Innovimax SARL
Consulting, Training  XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €


Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-06-03 Thread Ian Hickson
On Sat, 4 Apr 2009, Kristof Zelechovski wrote:

 It seems that getting the element name is not covered at all, it is a core
 interface, so definitions in the HTML specification do not apply.

I don't know what this is in reference to. Could you elaborate on what 
change to the spec you would like?

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'


Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-06-03 Thread Henri Sivonen

On Jun 3, 2009, at 09:45, Ian Hickson wrote:


On Sat, 4 Apr 2009, Innovimax SARL wrote:


In 2.3 Case-sensitivity and string comparison

Please replace

Converting a string to uppercase
and
Converting a string to lowercase

by respectively

Converting a string to uppercase ASCII
and
Converting a string to lowercase ASCII


Done.



Please fix the terminology under Writing HTML documents to match.

--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/




Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-06-03 Thread Kristof Zelechovski
The definition of uppercasing in HTML does not apply to element names
because getting them is covered by the DOM specification and not by the HTML
specification.  This is all right with me; I only think that saying to
uppercase ASCII explicitly is not necessary.
Chris



Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-04-04 Thread Kristof Zelechovski
I suppose that converting a string to uppercase is an action relevant only
to cases where only ASCII character set is allowed in the argument, such as
HTML element names.  Within this restricted application domain, converting
to uppercase has the same effect as converting to uppercase ASCII.

IMHO,

Chris



Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-04-04 Thread Innovimax SARL
Well that could be a good answer indeed

Now let's try to dig into the subtilties on Unicode

For example what does the spec says about an attribute whose name is
data-K (where we have this unicode sequence U+0064 U+0061 U+0074 U+0061
U+002D U+212A ) ?

Is it allowed ? If not why ?

That's why I think everywhere in the spec, where ASCII is meant, it should
be explicit. If not it would clash with a Unicode understanding

IMHO

Mohamed

On Sat, Apr 4, 2009 at 10:06 AM, Kristof Zelechovski
giecr...@stegny.2a.plwrote:

  I suppose that converting a string to uppercase is an action relevant
 only to cases where only ASCII character set is allowed in the argument,
 such as HTML element names.  Within this restricted application domain,
 converting to uppercase has the same effect as converting to uppercase
 ASCII.

 IMHO,

 Chris




-- 
Innovimax SARL
Consulting, Training  XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €


Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-04-04 Thread Kristof Zelechovski
data-* attributes allow XML name characters and they are converted to lower
case in HTML (ASCII, AIUI).

BTW, editorial correction for 3.3.3.8
http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html#embedd
ing-custom-non-visible-data : should be its name contains no characters in
the range (because an attribute contains its value).

Chris



Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-04-04 Thread Kristof Zelechovski
An attribute named data-K is allowed.



Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-04-04 Thread Innovimax SARL
Well again it depends if you read the spec with an ASCII point of view or a
Unicode point of view

If I read carefully the spec, it is explicitly said that

[[
3.3.3.8 Embedding custom non-visible data

A custom data attribute is an attribute whose name starts with the string
data-, has at least one character after the hyphen, is XML-compatible, has
no namespace, and contains no characters in the range U+0041 .. U+005A
(LATIN CAPITAL LETTER A .. LATIN CAPITAL LETTER Z).
]]

So

This sequence is allowed

data-K (where we have this unicode sequence U+0064 U+0061 U+0074 U+0061
U+002D U+212A )

but the following one is NOT

data-K (where we have this unicode sequence U+0064 U+0061 U+0074 U+0061
U+002D U+004B ) ?


That's why I was asking this question in particular

Mohamed

On Sat, Apr 4, 2009 at 11:05 AM, Kristof Zelechovski
giecr...@stegny.2a.plwrote:

  An attribute named data-K is allowed.




-- 
Innovimax SARL
Consulting, Training  XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €


Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-04-04 Thread Anne van Kesteren
On Sat, 04 Apr 2009 10:06:55 +0200, Kristof Zelechovski  
giecr...@stegny.2a.pl wrote:
I suppose that converting a string to uppercase is an action relevant  
only to cases where only ASCII character set is allowed in the argument,  
such as HTML element names.  Within this restricted application domain,  
converting to uppercase has the same effect as converting to uppercase  
ASCII.


That's not true. You can get Unicode characters in HTML element names.  
(You still want to lowercase only the ASCII characters though.)



--
Anne van Kesteren
http://annevankesteren.nl/


Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-04-04 Thread Innovimax SARL
Sorry, I don't see the answer to my question here !

On Sat, Apr 4, 2009 at 10:54 AM, Kristof Zelechovski
giecr...@stegny.2a.plwrote:

  data-* attributes allow XML name characters and they are converted to
 lower case in HTML (ASCII, AIUI).

 BTW, editorial correction for 
 3.3.3.8http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html#embedding-custom-non-visible-data:
 should be “*its name* contains no characters in the range” (because an
 attribute contains its value).

 Chris




-- 
Innovimax SARL
Consulting, Training  XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €


Re: [whatwg] Fwd: Remarks on HTML5 (ASCII / Unicode)

2009-04-04 Thread Kristof Zelechovski
It seems that getting the element name is not covered at all, it is a core
interface, so definitions in the HTML specification do not apply.
Chris