home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.std.internat:825 news.admin.misc:719
- Path: sparky!uunet!ogicse!uwm.edu!spool.mu.edu!hri.com!noc.near.net!nic.near.net!not-for-mail
- From: anselmo@nic.near.net (Ed Anselmo)
- Newsgroups: comp.std.internat,news.admin.misc
- Subject: Re: 8-bit news
- Message-ID: <1gft35INN771@nic.near.net>
- Date: 13 Dec 92 17:49:25 GMT
- Article-I.D.: nic.1gft35INN771
- References: <th0efeo@rhyolite.wpd.sgi.com> <1gdin0INN2rm@agate.berkeley.edu>
- <Bz6F6z.DvK@zoo.toronto.edu> <1992Dec13.100023.7056@clarinet.com>
- Organization: NEARnet, Cambridge, MA
- Lines: 17
- NNTP-Posting-Host: nic.near.net
- In-reply-to: brad@clarinet.com's message of Sun, 13 Dec 1992 10:00:23 GMT
-
- >>>>> In article <1992Dec13.100023.7056@clarinet.com>,
- >>>>> brad@clarinet.com (Brad Templeton) writes:
-
- Brad> For things like rich text, non-ASCII characters, I agree that
- Brad> using encodings that fit into ASCII is a good idea.
-
- Brad> However, when it comes to graphics and other binary information
- Brad> in multimedia news articles, I find this to be too much of a
- Brad> kludge in the service of old software.
-
- Where does MIME say that you have to use a 7-bit encoding? If you
- look in RFC 1341, you'll see that MIME doesn't preclude the use of
- 8-bit clean transports.
-
- With graphics/sound/smell (name your favorite multimedia thingy), you
- still have to encode content-type, just like you do with richtext and
- non-ascii characters. MIME provides a way to do this.
-