Re: request from HTTP draft editors for charset registration element
Ned Freed <Ned.Freed@innosoft.com> Mon, 29 April 1996 10:55 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08163; 29 Apr 96 6:55 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08159; 29 Apr 96 6:55 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa05284; 29 Apr 96 6:55 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id GAA28302; Mon, 29 Apr 1996 06:24:58 -0400
Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by list.cren.net (8.6.12/8.6.12) with ESMTP id GAA28201 for <ietf-822@list.cren.net>; Mon, 29 Apr 1996 06:22:58 -0400
Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V5.0-7 #8694) id <01I43CG6X3TCA734XK@INNOSOFT.COM>; Mon, 29 Apr 1996 03:22:01 -0700 (PDT)
Message-Id: <01I43KV17UTCA734XK@INNOSOFT.COM>
Date: Mon, 29 Apr 1996 03:20:13 -0700
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ned Freed <Ned.Freed@innosoft.com>
To: Larry Masinter <masinter@parc.xerox.com>
Cc: ietf-822@list.cren.net, jg@w3.org
Subject: Re: request from HTTP draft editors for charset registration element
In-Reply-To: "Your message dated Thu, 25 Apr 1996 17:15:03 -0700 (PDT)" <96Apr25.171514pdt.2733@golden.parc.xerox.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Content-transfer-encoding: 7bit
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN
> (I'm told this is the right list to comment on MIME registration > procedures, e.g., draft-ietf-822ext-mime-reg-03.txt). > In the course of preparing the HTTP 1.1 draft, we wanted to suggest > some preferred names for charsets as registered by IANA. The concept of a "primary name" whose use is preferred over any other name has been part of the draft procedure for some time. I think this meets your criteria for a preferred name. > Right now, charsets are registered with many aliases. However, for use > in HTTP, all of the aliases are really cumbersome. We would like > senders to preferentially send > ISO-8859-1 > instead of any of the other aliases for that charset. > Is this a possibility? See above -- I think it is already a done deal. (Unless someone objects, of course.) > Where is the revised charset registration specification, since it > isn't in reg-03? It has been submitted as an I-D and should be out shortly. Ned
- request from HTTP draft editors for charset regis… Larry Masinter
- Re: request from HTTP draft editors for charset r… Ned Freed
- Re: request from HTTP draft editors for charset r… Larry Masinter
- Re: request from HTTP draft editors for charset r… Ned Freed