- From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>
- Date: Fri, 25 Mar 1994 10:58:13 +0900 (JST)
- To: David_Goldsmith@taligent.com (David Goldsmith)
- Cc: ietf-charsets@INNOSOFT.COM
> Although those of you on the IETF announcements list will already have seen > it, I wanted to draw attention to the new version of the UTF-7 (mail safe > Unicode in MIME) document posted as an internet draft > (draft-goldsmith-mime-utf7-02.{txt,ps}). Are you joking? Just as Keith said: :It's impractical to :support the entirety of ISO 2022 (new charsets can always be added), so a :client needs to know which of the charsets are being used before it can :decide whether to display the body part. it is impractical to support the entirety of ISO 10646. In short, a client needs to know which of the characters are being used before it can decide whether to display the body part. See draft-ohta-mime-charset-names-00.txt for the detail on how impractical it is with existing implementations. Masataka Ohta PS As your proposal is bad enough already, I don't think I must point out other prolems of the proposal. --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
Received on Thursday, 24 March 1994 18:05:41 UTC