Re: PDFs not encoded as base64
- From: "Steve Cochran" <scochran@xxxxxxxxxx>
- Date: Thu, 9 Feb 2006 14:38:20 -0500
You might be able to fake out the system via changing the registry information.
Go to
HKEY_CLASSES_ROOT\.pdf
and change the
Content type application/pdf
to
application/octet-stream
which is what is used for generic binary files.
See then how OE embeds the pdf file. If that fixes it, then make sure that change didn't affect Acrobat or any other program that uses pdf files. I don't think it will.
steve
"oobayly" <oobayly@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B2EFC61E-3FBF-44F7-93F7-43C92A4CAA19@xxxxxxxxxxxxxxxx
Michael,
Thanks for the response, I had kinda guessed the OE isn't looking to far
down the file, the 1st 520 odd bytes are plain ascii and then the binary data
begins. This is in a 85KB pdf, so it's a tiny percentage that is ascii (0.01%
in fact).
Out pdfs have several embedded fonts & images, so I'd have hoped that OE
could pick this up.
Regarding your solution, zipping was my 1st thought, but not a viable option
in our office. We also prefer sending mails in html, so UUencoding is not
ideal, as you said.
Maybe it's a good excuse to get Thunderbird on everyones machines.
"Michael Santovec" wrote:
OE decides on Base64 or quoted-printable encoding based on the file
contents. If the beginning of the file is mostly simple text, it uses
Quoted-printable.
If you look at the PDF file in Notepad, you'll see what OE sees.
This probably typically occurs with small, simple PDF files. Larger PDF
files including those with various fonts and graphics will be sent in
Base64.
A couple of things you can do, but neither of them great:
Use Uuencode rather than MIME in the mail sending format. But this
isn't idea and isn't compatible with HTML messages.
Or Zip the PDF file before sending. That will force the Base64. But
the recipient will have to unzip it.
--
Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm
"oobayly" <oobayly@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72D6E4F3-76EF-44F1-9A4B-5701B6E7E43B@xxxxxxxxxxxxxxxx
> I'm using OE6 (6.00.2800.1123) on Win2K SP4, everything is up to date.
> When I send an email with a pdf attached, it is being attached with
> the
> headers:
> Content-Type: application/pdf;
> name="200411SB1043-S-0.pdf"
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: attachment;
> filename="200411SB1043-S-0.pdf"
>
> When this email is received by a Hotmail recipient, the pdf is
> corrupt. I've
> compared the original and received pdf, and certain lines of data are
> being
> truncated. Hence the corruption.
>
> I've checked, and as expected other binary attachments are being
> encoded in
> base64. Admittedly, Hotmail is the only client that appears to corrupt
> the
> file, but this encoding behaviour shouldn't be occuring. A PDF not
> always,
> but will often contain binary data, and should be encoded in base64 to
> get
> around this type of problem.
>
> Many thanks
> John
>
.
- Follow-Ups:
- Re: PDFs not encoded as base64
- From: Michael Santovec
- Re: PDFs not encoded as base64
- References:
- Re: PDFs not encoded as base64
- From: Michael Santovec
- Re: PDFs not encoded as base64
- From: oobayly
- Re: PDFs not encoded as base64
- Prev by Date: Re: Outlook Express Offline on start up
- Next by Date: Re: hyperlink problem
- Previous by thread: Re: PDFs not encoded as base64
- Next by thread: Re: PDFs not encoded as base64
- Index(es):
Relevant Pages
|
