Re: Accept-Charset support

To: Francois Yergeau <yergeau@alis.com>
Subject: Re: Accept-Charset support
From: Klaus Weide <kweide@tezcat.com>
Date: Mon, 9 Dec 1996 22:44:05 -0600 (CST)
cc: www-international@w3.org
From www-international-request@www10.w3.org Mon Dec 9 23: 43:57 1996
In-Reply-To: <2.2.32.19961209230513.006cb34c@genstar.alis.ca>
Message-ID: <Pine.SUN.3.95.961209223033.22922K-100000@huitzilo.tezcat.com>
X-List-URL: http://www.w3.org/pub/WWW/Archives/Public/www-international

On Mon, 9 Dec 1996, Francois Yergeau wrote:
> À 02:19 07-12-96 -0600, Klaus Weide a écrit :
> >On Fri, 6 Dec 1996, Chris Lilley wrote:
> >> UNICODE-1-1-UTF-8 does not appear to be registered; although RFC 1641
> >> postulates it as a theoretical entity,  RFC 2044 (not yet diffused to all
> >> mirrors) specified UTF-8.
> >
> >It was there, until around the time when RFC 2044 got published.  
> >At that point UNICODE-1-1-UTF-8 disappeared without any trace from
> >the registry, and UTF-8 appeared instead.
> 
> This is wrong, "UNICODE-1-1-UTF-8" was never in the IANA registry, which is
> the reason I wrote up RFC 2044 in the first place: to get UTF-8 registered
> as a legitimate charset.

I apologize for having given factually false information.  I was going
by memory, which was apparently faulty.
  
[...] 
> >And note that RFC 2044
> >has just "Informational" status.
> 
> Which is the correct status for a document supporting a charset
> registration.

Yes, I only mentioned it because I was under the (false) impression that
the registration of "UTF-8" had superseded an earlier one for the longer
name. 

  Klaus

References:

Re: Accept-Charset support

From: Francois Yergeau <yergeau@alis.com>

Prev: Re: Accept-Charset support
Next: Re: Accept-Charset support
Index: Message index of www-international@w3.org mailing list
Thread: Thread index of www-international@w3.org mailing list