Re: [whatwg] Character casing for "Appropriate End Tags" and the "temporary buffer"

2009-10-29 Thread Matt Hall
Of course :-). Thanks a lot, Geoffrey!

-Matt

-Original Message-
From: Geoffrey Sneddon [mailto:gsned...@opera.com] 
Sent: Thursday, October 29, 2009 8:59 AM
To: Matt Hall
Cc: whatwg@lists.whatwg.org
Subject: Re: [whatwg] Character casing for "Appropriate End Tags" and the 
"temporary buffer"

Matt Hall wrote:
> Apologies for the repost -- here is the original e-mail in plain text:
> 
> 
> Prior to r4177, the matching of tag names for exiting the RCDATA/RAWTEXT 
> states was done as follows:
> 
> "...and the next few characters do no match the tag name of the last start 
> tag token emitted (compared in an ASCII case-insensitive manner)"
> 
> However, the current revision doesn't include any comment on character casing 
> in its discussion of "Appropriate End Tags."  Similarly, certain tokenizer 
> states require that you check the contents of the "temporary buffer" against 
> the string "script" but there is no indication of whether or not to do this 
> in a case-insensitive manner.
> 
> In both cases, should this comparison be done in an ASCII case-insensitive 
> manner or not? It might be helpful to clarify the spec in both places in 
> either case.

It is already case-insensitive as you lowercase the characters when 
creating the token name and when adding them to the buffer.


-- 
Geoffrey Sneddon - Opera Software
<http://gsnedders.com/>
<http://www.opera.com/>



Re: [whatwg] Character casing for "Appropriate End Tags" and the "temporary buffer"

2009-10-29 Thread Geoffrey Sneddon

Matt Hall wrote:

Apologies for the repost -- here is the original e-mail in plain text:


Prior to r4177, the matching of tag names for exiting the RCDATA/RAWTEXT states 
was done as follows:

"...and the next few characters do no match the tag name of the last start tag token 
emitted (compared in an ASCII case-insensitive manner)"

However, the current revision doesn't include any comment on character casing in its discussion of 
"Appropriate End Tags."  Similarly, certain tokenizer states require that you check the contents of 
the "temporary buffer" against the string "script" but there is no indication of whether 
or not to do this in a case-insensitive manner.

In both cases, should this comparison be done in an ASCII case-insensitive 
manner or not? It might be helpful to clarify the spec in both places in either 
case.


It is already case-insensitive as you lowercase the characters when 
creating the token name and when adding them to the buffer.



--
Geoffrey Sneddon — Opera Software




Re: [whatwg] Character casing for "Appropriate End Tags" and the "temporary buffer"

2009-10-29 Thread Matt Hall
Apologies for the repost -- here is the original e-mail in plain text:


Prior to r4177, the matching of tag names for exiting the RCDATA/RAWTEXT states 
was done as follows:

"...and the next few characters do no match the tag name of the last start tag 
token emitted (compared in an ASCII case-insensitive manner)"

However, the current revision doesn't include any comment on character casing 
in its discussion of "Appropriate End Tags."  Similarly, certain tokenizer 
states require that you check the contents of the "temporary buffer" against 
the string "script" but there is no indication of whether or not to do this in 
a case-insensitive manner.

In both cases, should this comparison be done in an ASCII case-insensitive 
manner or not? It might be helpful to clarify the spec in both places in either 
case.

Thanks!
-Matt


[whatwg] Character casing for "Appropriate End Tags" and the "temporary buffer"

2009-10-29 Thread Matt Hall
Prior to r4177, the matching of tag names for exiting the RCDATA/RAWTEXT states 
was done as follows:



"...and the next few characters do no match the tag name of the last start tag 
token emitted (compared in an ASCII case-insensitive manner)"



However, the current revision doesn't include any comment on character casing 
in its discussion of "Appropriate End Tags."  Similarly, certain tokenizer 
states require that you check the contents of the "temporary buffer" against 
the string "script" but there is no indication of whether or not to do this in 
a case-insensitive manner.



In both cases, should this comparison be done in an ASCII case-insensitive 
manner or not? It might be helpful to clarify the spec in both places in either 
case.



Thanks!

-Matt