Re: Bug#3253: Pine over-encodes files (came from Bug#932)
On Thu, 13 Jun 1996, Richard Kettlewell wrote:
> It looks, from reading this, as if you've seriously confused MIME and
> BASE64. Please tell me this isn't true...
>
> I can see why Pine might lead one to believe that MIME and BASE64 were
> the same, given that it is so resistant to doing anything with MIME
> without also BASE64ing everything in sight.
>
Well, Base64 IS the encoding scheme used by Mime, right? The confusion is
over when an attachment (I read MIME here, right?) should Base64 encode a
file to be attached.
The Pine developers say: Gee, they want this included as an attachment,
they must need to protect it, so, let's encode it! If they didn't want it
encoded they would just have inserted it into the message!
There are, obviously, those in the group who object to this point of view
by the developers.
My primary advice is, if it hurts when you do that, then don't do that!
Seriously, use control R unless you REALLY want Base64 encoding. Then and
only then can you make it an attachment.
For those of you who can't deal with this solution, I can only say:
You and the Pine Developers go to neutral corners, and only come out
fighting after I have left the room. (I don't like religios wars)
Later,
Dwarf
------------ --------------
aka Dale Scheetz Phone: 1 (904) 877-0257
Flexible Software Fax: NONE
Black Creek Critters e-mail: dwarf@polaris.net
------------ If you don't see what you want, just ask --------------
Reply to: