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 299 - Special-Case Error Message for b0rken ;charset Values
Summary: Special-Case Error Message for b0rken ;charset Values
Status: NEW
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.6.1
Hardware: All All
: P2 enhancement
Target Milestone: 0.7.0
Assignee: Terje Bless
QA Contact: qa-dev tracking
URL: http://www.w3.org/mid/3f52499b.387220...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-27 07:26 UTC by Terje Bless
Modified: 2007-03-29 18:49 UTC (History)
0 users

See Also:

Attachments

Description Terje Bless 2003-08-27 07:26:18 UTC 
From Björn Höhrmann:

[On] http://members.aol.com one can find

  <meta http-equiv='Content-Type'
        content='text/html; charset=Shift_JIS,ISO-8859-1'>

I've now seen such constructs about half a dozen of times. As the comma
is not allowed in charset named, could the validator have a special case
for them with a more user friendly error message?