Re: PDF's as base64 vs. Q/P encoded attachments

[Graham Todd <gtodd@yorku.ca>]

>>>>> "Toby" == Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:

 Graham> Graham Todd <URL:mailto:gtodd@yorku.ca>

 0> In <URL:news:x67lo12n1p.fsf@ninga.ellerbeck.org>, Graham wrote:

 Graham> ... Gnus now tries to encode PDF's I create as Q/P ...

<snip>

 Toby> I wonder if PDF is sensitive to newline-mangling?  AIUI, PDF
 Toby> is based on Postscript, which should be okay, but it's
 Toby> possible that some application/* types need newlines
 Toby> preserving as "=0A=\n".  A pain!

 Toby> Could you check this hypothesis?  Compose a mail on a Unix
 Toby> platform, with two attachments - one q-p encoded normally,
 Toby> and one with newlines explicitly kept, as above (use
 Toby> query-replace or something, after MIME-encoding).  Then try
 Toby> reading both on a Windows platform.

I MIME encoded and then did the search replace and sent both as QP -
neither worked in Windows clients. Of course I might have screw

 Graham> I did something like this to fix it: (push
 Graham> '("application/pdf" base64)
 Graham> mm-content-transfer-encoding-alist) so that PDF's are
 Graham> always encoded base64.

Actually I think the correct line should be:

(push '("application/pdf" base64) mm-content-transfer-encoding-defaults)

It works for me (TM).

-- 
Graham Todd