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

[Bug 10854] New: willful violation of RFC2046 may be an exaggeration

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 13:59:07 +0000
To: public-html@w3.org
Message-ID: <bug-10854-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10854

           Summary: willful violation of RFC2046 may be an exaggeration
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/spec/Overview.html#writing-cac
                    he-manifests
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: julian.reschke@gmx.de
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


<http://dev.w3.org/html5/spec/Overview.html#writing-cache-manifests>:

"Note: This is a willful violation of two aspects of RFC 2046, which requires
all text/*  types to support an open-ended set of character encodings and only
allows CRLF line breaks. These requirements, however, are outdated; UTF-8 is
now widely used, such that supporting other encodings is no longer necessary,
and use of CR, LF, and CRLF line breaks is commonly supported and indeed
sometimes CRLF is not  supported by text editors. [RFC2046]"

But in <http://greenbytes.de/tech/webdav/rfc2046.html#rfc.section.4.1.2.p.4>:

"The specification for any future subtypes of "text" must specify whether or
not they will also utilize a "charset" parameter, and may possibly restrict its
values as well. For other subtypes of "text" than "text/plain", the semantics
of the "charset" parameter should be defined to be identical to those specified
here for "text/plain", i.e., the body consists entirely of characters in the
given charset. In particular, definers of future "text" subtypes should pay
close attention to the implications of multioctet character sets for their
subtype definitions."

So I don't see a conflict with respect to the charset parameter.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 30 September 2010 13:59:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:19 UTC