This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 803 - Output for ampersand-as-data warning is ill-formed
Summary: Output for ampersand-as-data warning is ill-formed
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.6.6
Hardware: Other other
: P2 normal
Target Milestone: 0.6.7
Assignee: Terje Bless
QA Contact: qa-dev tracking
URL: http://validator.w3.org/check?uri=htt...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-17 13:29 UTC by Bj
Modified: 2006-10-31 01:34 UTC (History)
0 users

See Also:

Attachments

Description Bj 2004-06-17 13:29:59 UTC 
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.websitedev.de%2Fmarkup%
2Fvalidator%2Ftests%2Fampersand-as-data.html

is not well-formed,

http://validator.w3.org/check?uri=http%3A%2F%2Fvalidator.w3.org%2Fcheck%3Furi%
3Dhttp%253A%252F%252Fwww.websitedev.de%252Fmarkup%252Fvalidator%252Ftests%
252Fampersand-as-data.html

  Line 60, column 30: character "&" is the first character
  of a delimiter but occurred as data
Comment 1 Bj 2004-06-17 14:50:52 UTC 
parse_errors(...) should be something like

...
      &add_warning($File, 'fake', 'Warning:',
        "Line $err->{line}, column $err->{char}: " . ent($errors[6])
...

to fix this.
Comment 2 Ville Skyttä 2004-06-18 12:56:19 UTC 
Applied to 0_6_0-branch.  Thanks.
Comment 3 Si^mon Pi^eters 2005-11-30 16:56:31 UTC 
Well-formedness errors are fatal, therefore it should return an error and not a
warning. An XML document cannot be valid if it is not well-formed.
Comment 4 Olivier Thereaux 2006-10-31 01:34:07 UTC 
comment #3 is not relevant to this bug, but to the "XML limitations" noted in validation results, and in http://esw.w3.org/topic/MarkupValidator/XML_Limitations

re-closing.