This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
<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.
Are you saying I should remove that note? (I'm not 100% clear on what you mean to have change because the note you cite doesn't mention "charset" at all but you say "I don't see a conflict with respect to the charset parameter".)
(In reply to comment #1) > Are you saying I should remove that note? (I'm not 100% clear on what you mean > to have change because the note you cite doesn't mention "charset" at all but > you say "I don't see a conflict with respect to the charset parameter".) What I'm trying to say is that the charset thingy is not in conflict with MIME at all, thus the note should just read: "Note: This is a willful violation of one aspect of RFC 2046, which requires all text/* types to only allow CRLF line breaks. This requirement, however, is outdated; use of CR, LF, and CRLF line breaks is commonly supported and indeed sometimes CRLF is not supported by text editors. [RFC2046]"
Oh by "charset" you meant character encodings? EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: I'm always happy to remove these notes.
Checked in as WHATWG revision r5578. Check-in comment: Remove a 'willful violation' note. http://html5.org/tools/web-apps-tracker?from=5577&to=5578