[reportlab-users] RE: Emailing Corrupting reportlab PDFs follow up

Matej Pivoluska reportlab-users@reportlab.com
Fri, 28 May 2004 01:42:53 +0200

D=F2a =A9tvrtok 27 M=E1j 2004 14:16 Michael Porter nap=EDsal(a):

Is it possible not to ASCII85 encode every object? I think when Outlook wil=
see non-ascii data (flate encoded stream), it will handle PDF correctly as=
binary file.


> I've done some investigation into this and it seems that Outlook is really
> to blame here...
> When you send a PDF attachment from Outlook with the default settings it
> encodes the PDF as quoted-printable but doesn't explicitly encode the CRLF
> (with a =3D0D=3D0A sequence). The receiving client will then presumably a=
> that the line ending characters are unimportant and use those native to t=
> platform (which will result in a corrupt PDF on Unix or Macs).
> So the problem is that Outlook is regarding the PDF as text rather than
> binary. Outlook appears to ignore the mime-type/file extension when
> deciding on what encoding to use but instead tries to guess from the file
> content. Presumably the "random" element comes in because some PDFs look
> more "binary" than others.
> A workaround is to zip up the PDF or set Options|Mail
> Format|Settings|Message Format to UUEncode.
> The the real solution would be tell Outlook to always regard .PDF files as
> binary (and hence use base64 encoding). Unfortunately I don't know how to
> do this or even if it's possible. If anyone does, please let me know.
> Michael Porter
> ReportLab
> _______________________________________________
> reportlab-users mailing list
> reportlab-users@reportlab.com
> http://two.pairlist.net/mailman/listinfo/reportlab-users