Re: Problem with base64 encoding

On 12/13/2008 01:32:24 PM, Pawel Salek wrote:
> On 12/13/2008 10:15:36 PM, Geoffrey Leach wrote:
> > The attached file (produced by an over-zealous email client, but  
> > that's
> > another story) has the following content:
> > 
> > MIME-Version: 1.0
> > Content-Type: application/octet-stream
> > Content-Transfer-Encoding: base64
> > 
> > Balsa sees this text/x-vdhl whatever that is. I would think that
> Balsa
> > should be able to decode it, or, at very least give a better
> > diagnostic.
> I think something has happened during transmission because the 
> message
> you attached makes no references to text/x-vdhl that I see. The
> message  
> consists of one part only. This single part has the type of  
> application/octet-stream. I can save it just fine on a disk and then
> it  
> looks quite sensibly like a text file with some escape sequences  
> inserted. When I manually modify content-type to read text/plain,
> balsa  
> displays it inline without any problem - base64 decoding works  
> flawlessly.
> Could you please describe in more detail the problem you see, maybe  
> providing snapshots, if they would be informative?

That's the point, exactly. Should Balsa not just do it? The screenshot 
you request is attached.

Attachment: Screenshot-Balsa-zdump.png
Description: PNG image

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]