Article View: comp.mail.multi-media
Article #199Re: MIME (RFC1341) Charset question
From: Nathaniel Borenstein
Date: Fri, 09 Oct 1992 13:47
Date: Fri, 09 Oct 1992 13:47
16 lines
1232 bytes
1232 bytes
Excerpts from mail: 8-Oct-92 Re: MIME (RFC1341) Charset .. Jon Postel@ISI.EDU (98) > I'd like to see a move to unify MIME charactersets with those listed in > RFC-1345. Well, I'm not sure what you mean by "unify". MIME has been strongly biased towards keeping the number of charsets as low as possible, while RFC 1345 provides a fairly exhaustive survey of what character sets are in use. I think it would be a mistake if MIME provided a blanket "seal of approval" for ALL of those character sets -- the fewer redundant character sets, the better, in my opinion. However, if all you're saying is that the character sets that DO overlap should be called by the same name in the two documents, I certainly have no problem with that! -- Nathaniel
Technical Details
Message-ID:
<gepMpeG0M2Yt47Fn5s@thumper.bellcore.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!THUMPER.BELLCORE.COM!nsbReferences:
<199210090106.AA28791@zephyr.isi.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!THUMPER.BELLCORE.COM!nsb From: nsb@THUMPER.BELLCORE.COM (Nathaniel Borenstein) Newsgroups: comp.mail.multi-media Subject: Re: MIME (RFC1341) Charset question Message-ID: <gepMpeG0M2Yt47Fn5s@thumper.bellcore.com> Date: 9 Oct 92 13:47:22 GMT References: <199210090106.AA28791@zephyr.isi.edu> Sender: usenet@ucbvax.BERKELEY.EDU Distribution: inet Organization: The Internet Lines: 16