W3C home > Mailing lists > Public > ietf-charsets@w3.org > April to June 2000

Re: Fwd: Registration of 6 charsets

From: <ned.freed@innosoft.com>
Date: Tue, 04 Apr 2000 09:25:56 -0800 (PST)
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: "Martin J. Duerst" <duerst@w3.org>, Harald Alvestrand <Harald@Alvestrand.no>, ietf-charsets@innosoft.com
Message-id: <01JNU0CMI10U0006J9@MAUVE.INNOSOFT.COM>
> > > >     Four of them are declared not suitable for use in MIME
> > > >
> > > >         While it is not unclear when one should say "not suitable
> > > >         for use in MIME", one can automatically make a charset
> > > >         not shuitable for use in MIME by using some characters
> > > >         in the charset name, anyway

This is incorrect. All charset names MUST be usable as a MIME
charset parameter value. The process forbids registration of anything
else. See RFC 2278, section 3.3.

> > This is a completely confused comment. All of the registrations
> > are suitable for use with MIME, because all of them allow to
> > respect the CR/LF conventions of MIME.

> I'm afraid you are completely confused. I can see no requirement of
> "CR/LF conventions" neither in RFC2278 nor for the suitability
> for MIME use.

Martin is completely correct here. See RFC 2278 section 3.1. It says that all
charset registrations must note whether or not they are suitable for use in
MIME text, based on what the MIME specification (RFC 2045) says about text. The
two restrictions RFC 2045 imposes are that line terminators must be represented
as CRLF and that nulls may not be used. As far as I can tell these charsets
meet these restrictions, so they are suitable for MIME use, and if that's the
case that's what the registration has to say. (As it happens I wrote this
and I can assure you that this is what's intended.)

This is an entirely mechanical assessment based on the technical properties of
the charset. You appear to be confusing it with whether or not you feel these
charsets _should_ be used in MIME. That's a separate concern, and not one
that the registration process addresses.

Received on Tuesday, 4 April 2000 14:28:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:52:17 UTC