W3C home > Mailing lists > Public > www-style@w3.org > October 2012

[css2.1] tokenizer syntax - handling escaped null in badstring

From: Glenn Adams <glenn@skynav.com>
Date: Sat, 6 Oct 2012 11:58:57 +0800
Message-ID: <CACQ=j+dejp3yivmT=MrzPvXcwt=wCZnFdCvg=q70fQ7-VkwQvA@mail.gmail.com>
To: W3C Style <www-style@w3.org>
The current tokenizer syntax [1] specifies:

escape		{unicode}|\\[^\r\n\f0-9a-f]
badstring1      \"([^\n\r\f\\"]|\\{nl}|{escape})*\\?

Given the following input string:

< U+0022 (QUOTATION MARK), U+005C (REVERSE SOLIDUS), U+0000 (NULL) >

Does the < U+005C, U+0000 > match escape or does it match the final \\? ?
That is, should U+0000 be treated as an escapable character or as EOF
(EOS)? The above grammar suggests the former.

[1] http://www.w3.org/TR/CSS2/grammar.html
Received on Saturday, 6 October 2012 03:59:46 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:01 GMT