<HTML>
<HEAD>
<TITLE>Re: Why can't Windows users open my pdf files?</TITLE>
</HEAD>
<BODY>
<FONT FACE="Lucida Grande, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Thanks guys for your suggestions.<BR>
<BR>
To Kirk: Yes, I added the extension.<BR>
<BR>
To Richard: I will have to ask them to test that trick.<BR>
<BR>
To Stoller: Encoding for Windows is supposed to strip away the resource fork. How else can I do it?<BR>
<BR>
To Milton: I did both ways, with the same result.<BR>
<BR>
To Linda: I found out about Little Snitch and upgraded. It did not solve the problem.<BR>
<BR>
To kobay: I can’t depend on all recipients opening Acrobat first. Too complicated to make sure they do.<BR>
<BR>
<BR>
I traced back to the original Word-document I had based the pdf on. It had a header with a logo that I found was made up of 2 identical logos on top of each other. I deleted the extra logo and moved the other a bit away from the edge of the document. That was all that was needed to create a functional pdf.<BR>
<BR>
It seems to me that Word can handle having images slightly outside the printable area, but that turning them into a pdf corrupts the resulting file. I have never seen this before – until I switched to Tiger.<BR>
<BR>
Maybe some more testing can confirm my conclusions? <BR>
<BR>
Tut<BR>
</SPAN></FONT>
</BODY>
</HTML>