From: Laurence Lundblade <lgl(_at_)qualcomm(_dot_)com>
Subject: Re: New versions of the drafts: please read
Date: Wed, 10 Sep 1997 16:57:52 -0700
Does "registered character set" mean one of character sets found in
"ftp://ftp.isi.edu/in-notes/iana/assignment/character-sets/";?
If so, you should change this sentence. "ISO-2022-JP" and "EUC-JP" is
registered by IANA. But to canonicalize Japanese text, "ISO-2022-JP"
MUST be used if it is transfered by SMTP.
Kazu, can you write some language here?
Do you mean to post ISO-2022-JP messages to ietf-smime? If so, I'm
afraid that most of members cannot read it.
# It seems that many people cannot decode even my From: field.
Or someone else that knows the
char set stuff better.
I think I know charset well.
Let me clarify my point. There are three major charset in Japan,
ISO-2022-JP(aka JIS), EUC/Japan, Shift-JIS. In SMTP world, only
ISO-2022-JP text is allowed to transfer. However, in HTTP world, all
three charsets are actually transferred. Seeing this situation, it
seems to me that "registered character set" is confusing.
NOTE: in S/MIME draft, the word "charset" SHOULD be used. Its
definition can be found in draft-freed-charset-reg-02.txt. Please
understand that ISO 2022 is an encoding scheme for character sets.
Sounds right, perhaps combined with the above text, and alluding to the
fact that 2022 is Japanese so other implementors that don't know about
Japanese don't get confused.
2022 includes Kerean and Chinese as well as Japanese. People says that
EUC/Korea is the transfer charset in Korea but international gateways
convert EUC/Korea to ISO-2022-KR. Are there any Korean guys on this
list?
--Kazu