[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Registering GBK and GB18030 in the IANA charset registry - MIMEsuitability
- To: Bruno Haible <[email protected]>
- Subject: Re: Registering GBK and GB18030 in the IANA charset registry - MIMEsuitability
- From: Markus Scherer <[email protected]>
- Date: Mon, 12 Nov 2001 17:33:35 -0800
- Cc: Anthony Fok <[email protected]>, [email protected],Kevin Lau <[email protected]>, Fai <[email protected]>,James Su <[email protected]>, Shouhua Wang <[email protected]>,Jian Wu <[email protected]>, Leon Zhang <[email protected]>,Yu Guanghui <[email protected]>, Roger So <[email protected]>,Pablo Saratxaga <[email protected]>, zhaoway <[email protected]>,Yu Mingjian <[email protected]>, Chen Xiangyang <[email protected]>,Dirk Meyer <[email protected]>, Ken Lunde <[email protected]>,[email protected], [email protected]
- Organization: IBM
- References: <20011109144947.A4932@sunrise> <20011109162100.A4954@sunrise><[email protected]>
- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4)Gecko/20011019 Netscape6/6.2
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...
markus