W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2010

[Bug 8606] ambiguous ampersand does not include character references

From: <bugzilla@wiggum.w3.org>
Date: Tue, 26 Jan 2010 07:56:12 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NZgHU-00010C-FV@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8606


Don Brutzman <brutzman@nps.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




--- Comment #2 from Don Brutzman <brutzman@nps.edu>  2010-01-26 07:56:10 ---
wellll, i guess if you strictly parse the linked definition of
<a href="#syntax-text" title="syntax-text">text</a>,
then the complete character reference only comprises a single
<a href="#syntax-text" title="syntax-text">text</a>
character.  nevertheless the individual characters that follow that initial
ampersand within a character reference would otherwise be considered plain text
if they weren't in that context.

due to overloaded terminology, this logic can get convoluted and doesn't seem
immediately obvious to a reader trying to understand the definition.

re-reading the definition for ambiguous ampersand still seems to me to include
the characters making up character reference.

inserting the phrase "that is not a valid character reference" explictly
disambiguates such a possible misperception and reinforces the sense of the
definition.  thus i again suggest inserting that phrase.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 26 January 2010 07:56:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC