[rfc-i] New version: draft-hoffman-utf8-rfcs-04.txt

[Joe Touch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Stephane Bortzmeyer wrote:
> On Tue, Nov 04, 2008 at 12:28:51AM -0800,
>  Joe Touch <touch at ISI.EDU> wrote 
>  a message of 55 lines which said:
> 
>> Text/plain is ASCII;
> 
> Where does this strange idea come from? From not enough reading of RFC
> 2046?

- From actually *reading* 2046 ;-)

4.1.2.  Charset Parameter

   A critical parameter that may be specified in the Content-Type field
   for "text/plain" data is the character set.  This is specified with a
   "charset" parameter, as in:

     Content-type: text/plain; charset=iso-8859-1

   Unlike some other parameter values, the values of the charset
   parameter are NOT case sensitive.  The default character set, which
   must be assumed in the absence of a charset parameter, is US-ASCII.

>> UTF-8 creates the problem by deliberately overloading text/plain to
>> also mean UTF-8.
> 
> First time I hear that funny theory. Whether it is plain text or not
> is completely independant of the character set in use.

Yes. And the default charset for plain/text *is* US-ASCII.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkQbZ8ACgkQE5f5cImnZrvvngCgqcYL04g0qFyfXPh7D1cN9nxI
9w4AoP04lyOU99wa56hisQHbGW7T8+vP
=uf2s
-----END PGP SIGNATURE-----