[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Registration of new charset "UTF-16"

To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Registration of new charset "UTF-16"
From: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>
Date: Wed, 20 May 1998 10:37:49 +0900
Cc: duerst@w3.org (Martin J. Duerst), masinter@parc.xerox.com,erik@netscape.com, Chris.Newman@INNOSOFT.COM, ietf-charsets@ISI.EDU,murata@fxis.fujixerox.co.jp, Tatsuo_Kobayashi@justsystem.co.jp
In-reply-to: <199805191523.AAA15450@necom830.hpcl.titech.ac.jp>

Masataka Ohta wrote:
> Such labeling of data is explicitely forbidden for text types of MIME,
> which means that UTF-* and related RFCs are wrong and they are not
> MIME charsets.

Actually, the MIME-like mechanism of HTTP is exempt from the restrictions 
on the top-level media type "text".

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata@apsdc.ksp.fujixerox.co.jp

References:
- Re: Registration of new charset "UTF-16"
  - From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>

Prev by Date: Re: Registration of new charset "UTF-16"
Next by Date: International registry of coded character sets available on the web
Prev by thread: Re: Registration of new charset "UTF-16"
Next by thread: UTF-7
Index(es):
- Date
- Thread