X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,b01e20635782122b X-Google-Attributes: gidf996b,public From: kenter@cs.utwente.nl (Arjan Kenter) Subject: Re: DALMATIAN ASCII Please (large posting [not anymore]) Date: 1997/01/21 Message-ID: <5c3b4p$2c1@pandora.cs.utwente.nl>#1/1 X-Deja-AN: 211523576 distribution: world references: <32E2F583.193A@bc.sympatico.ca> <32E3CB5A.7EDF@online.no> organization: University of Twente, Dept. of Computer Science x-server-date: 21 Jan 1997 21:06:33 GMT newsgroups: alt.ascii-art In article <32E3CB5A.7EDF@online.no>, Erik Kambestad Veland writes: |> This is a multi-part message in MIME format. [ ... ] |> Content-Type: TEXT/PLAIN; charset=US-ASCII; name=101 |> Content-Transfer-Encoding: BASE64 |> Content-ID: |> Content-Description: |> |> DQoNCg0KDQoNCj4+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg Uhm.. excuse me for not being able to fully understand your deepest thoughts, but why do you post ASCII art in base 64 encoding? The purpose of base 64 is to transmit binary data in, uhm, ASCII format (alright, alright, it uses a subset of the 7-bit ASCII character set). Of course, this has nothing to do with the quality of your posts, which is good as always, but it is a bit a of nuisance to decode them. Especially since the posts (like the one I quoted) are not MIME compliant (you're losing boundaries) so that they need to be fixed manually. And then there is the over 33% overhead of base 64 encoding over plain ASCII transmission.. (Or does the 72 column limit still strike?) Just thought I'd mention this - nothing personal :-) -- ^^ ir. H.J.H.N. Kenter oo ) kenter@cs.utwente.nl University of Twente =x= \ tel. +31 53 4894099 Tele-Informatics & Open Systems | \ tfx. +31 53 4893247 P.O. Box 217 7500 AE Enschede /|__ \ The Netherlands (____)_/ http://www.cs.utwente.nl/~kenter/ Famous last words: Segmentation Fault (core dumped)