- From: Coralie Mercier <coralie@w3.org>
- Date: Wed, 16 Jun 2021 23:05:22 +0200
- To: Brandon Horsley <whorsley@vt.edu>
- Cc: site-comments@w3.org
Hello Brandon, The spec you referenced has been superseded last January, so you should be looking at this instead: https://html.spec.whatwg.org/#character-reference-state where I believe the incorrect reference is not to be seen anymore. In case it’s useful: How to find the right spec to use when one is superseded? From the top of the Table of Contents, click the “Table of contents” link which will take you to the front of the spec. From there, look for “latest published version”s. Coralie > On 17 May 2021, at 19:17 , Brandon Horsley <whorsley@vt.edu> wrote: > > In example 13 under 8.2.4.72 at > https://www.w3.org/TR/html52/syntax.html#character-reference-state it > looks as though the & was accidentally referenced as &amp; twice. > > I think: > But if the markup was I'm &notin; I tell you, the character > reference would be parsed as "notin;", resulting in I'm ∉ I tell you > (and no parse error). > Was meant to be: > But if the markup was I'm ∉ I tell you, the character reference > would be parsed as "notin;", resulting in I'm ∉ I tell you (and no > parse error). > > And the last line of the example: > However, if the markup contains the string I'm &notit; I tell you > in an attribute, no character reference is parsed and string remains > intact (and there is no parse error). > Was meant to be: > However, if the markup contains the string I'm ¬it; I tell you in > an attribute, no character reference is parsed and string remains > intact (and there is no parse error). > > Apologies if I am just confused and this was intentional. > > -- Brandon -- Coralie Mercier - W3C Marketing & Communications - https://www.w3.org mailto:coralie@w3.org +337 810 795 22 https://www.w3.org/People/Coralie/
Received on Wednesday, 16 June 2021 21:05:56 UTC