W3C home > Mailing lists > Public > www-international@w3.org > July to September 2003

RFC 2045 vs RFC 2231 in HTML 4.01 17.13.4(form)

From: Jungshik Shin <jshin@i18nl10n.com>
Date: Fri, 25 Jul 2003 16:30:10 -0400 (EDT)
To: <www-html-editor@w3.org>
cc: <www-international@w3.org>
Message-ID: <Pine.BSO.4.33.0307251611360.19869-100000@callisto.jtan.com>

Hello,

I found that HTML 4.01 17.13.4 refers to RFC 2045 where it should
have referred to RFC 2231.

H4> a name attribute specifying the control name of the corresponding
H4> control. Control names originally encoded in non-ASCII character
H4> sets may be encoded using the method outlined in [RFC2045].

H4> The user agent should attempt to supply a file name for each submitted
H4> file. The file name may be specified with the "filename" parameter
H4> of the 'Content-Disposition: form-data' header, or, in the case of
H4> multiple files, in a 'Content-Disposition: file' header of the
H4> subpart. If the file name of the client's operating system is not
H4> in US-ASCII, the file name might be approximated or encoded using
H4> the method of [RFC2045].

RFC 2045 is about the format of the MIME message _body_ so that
it doesn't mention anything about the way characters encoded
in non-ASCII MIME charsets should be represented in  parameters of MIME
header field (e.g. 'filename' or 'name' in Content-Disposition header).
It's RFC 2231 that specifies how to specify parameter values in
non-ASCII MIME charsets.

I went through errata to HTML 4.01, but this error is not listed. It'd be
nice if this error is added to errata.

Thank you,

Jungshik Shin
Received on Friday, 25 July 2003 16:30:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:00 GMT