W3C home > Mailing lists > Public > www-validator@w3.org > August 2007

RE: Validator case-sensitive bug for CHARSET?

From: McDonald, Ira <imcdonald@sharplabs.com>
Date: Tue, 7 Aug 2007 12:33:30 -0700
Message-ID: <FCC7D7D1DB94054EB491EED9D274727D030F89@wabex2.sharpamericas.com>
To: "David Dorward" <david@dorward.me.uk>, "Ernest Unrau" <ejunrau@mts.net>
Cc: "www-validator Community" <www-validator@w3.org>, <www-international@w3.org>

Hi,

Quoting HTTP/1.1 (RFC 2616), page 22:

>> "HTTP character sets are identified by case-insensitive tokens. The
    complete set of tokens is defined by the IANA Character Set registry
    [19]."

And the normative IANA Charset Registration Procedures (RFC 2978),
page 4 says:

  "Finally, charsets being registered for use with the "text" media type
   MUST have a primary name that conforms to the more restrictive syntax
   of the charset field in MIME encoded-words [RFC-2047, RFC-2184] and
   MIME extended parameter values [RFC-2184].  A combined ABNF
   definition for such names is as follows:

     mime-charset = 1*mime-charset-chars
     mime-charset-chars = ALPHA / DIGIT /
                "!" / "#" / "$" / "%" / "&" /
                "'" / "+" / "-" / "^" / "_" /
                "`" / "{" / "}" / "~"
>>   ALPHA        = "A".."Z"    ; Case insensitive ASCII Letter
     DIGIT        = "0".."9"    ; Numeric digit"

Any use of IANA charset tags in any standard that is case 
sensitive is broken.

Cheers,
- Ira - editor of IANA Charset MIB (RFC 3808)

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com

-----Original Message-----
From: www-international-request@w3.org
[mailto:www-international-request@w3.org]On Behalf Of David Dorward
Sent: Tuesday, August 07, 2007 2:59 AM
To: Ernest Unrau
Cc: www-validator Community; www-international@w3.org
Subject: Re: Validator case-sensitive bug for CHARSET?



On 7 Aug 2007, at 08:11, Ernest Unrau wrote:
> No HTML tags are case-sensitive, but it may indeed be that the CHARSET
> parameter must be case sensitive since I'm told that the META tags are
> mimicking HTML headers. Perhaps the servers that parse these  
> headers are
> also case sensitive? But one would think that validation would fail on
> other META tags also.

There aren't any other meta tags that provide information needed in  
order to parse a document, so that isn't the case.

-- 
David Dorward
http://dorward.me.uk/
http://blog.dorward.me.uk/




No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.11.8/940 - Release Date: 8/6/2007 4:53 PM
 
Received on Tuesday, 7 August 2007 19:33:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:25 GMT