W3C home > Mailing lists > Public > ietf-charsets@w3.org > October to December 2001

Re: Registering GBK and GB18030 in the IANA charset registry - MIME suitability

From: Markus Scherer <markus.scherer@jtcsv.com>
Date: Mon, 12 Nov 2001 17:33:35 -0800
To: Bruno Haible <haible@ilog.fr>
Cc: Anthony Fok <anthony@thizlinux.com>, ietf-charsets@iana.org, Kevin Lau <kevin@thizlinux.com>, Fai <fai@thizlinux.com>, James Su <suzhe@turbolinux.com.cn>, Shouhua Wang <shwang@sonata.iscas.ac.cn>, Jian Wu <jwu@sonata.iscas.ac.cn>, Leon Zhang <leon@xteamlinux.com.cn>, Yu Guanghui <ygh@dlut.edu.cn>, Roger So <roger.so@sw-linux.com>, Pablo Saratxaga <pablo@mandrakesoft.com>, zhaoway <zw@debian.org>, Yu Mingjian <yumingjian@china.com>, Chen Xiangyang <chenxy@sun.ihep.ac.cn>, Dirk Meyer <dmeyer@adobe.com>, Ken Lunde <lunde@adobe.com>, li18nux2000@li18nux.org, bsd-locale@haun.org
Message-id: <3BF0786F.5010304@jtcsv.com>
Bruno Haible wrote:

> ...
> imply that mails should better be sent in UTF-8 encoding than in
> GB18030 encoding. Because then the interoperability with mailers that
> don't include a GB18030 converter is increased.
> Therefore I would suggest to remove the "suitable for use in MIME"
> sentence.

In terms of the IANA registration and of RFC 2978, "suitable for use in MIME" only requires a byte-based encoding where CR and LF have the usual ASCII control code values and byte values of 0 are only used for the NUL control code.
This makes GB 18030 "suitable for use in MIME".
The exact conditions are listed in RFC 2045.

The registration does not call for how easy it is to support a charset...

Received on Monday, 12 November 2001 20:37:08 UTC

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