schmidhauser wrote:
I must have been imprecise. The file has been produced by a reputable Press called Springer and may be downloaded by anyone with a subscription from SpringerLink (www.springerlink.com/content/0039-3215). They have thousands such files in their repositories. I'm neither the creator nor the author of that particular paper. (Which of course also means that I have no idea how the file was exported; but the creator was certainly not running 10.6.7.) Please do NOT submit this paper. You may take one which is in open access:
http://www.springerlink.com/content/0039-3215/open/
OK. This is a document you've mucked around with. I have asked the hosts to edit your original post and remove that link. I wouldn't want you to get into any copyright trouble by distributing something that you don't have rights to. In the future, use e-mail for any such files that shouldn't be public. Some of us do that all the time.
What happened is that I downloaded the file in question last week, while I was still running 10.6.7. Merely opening and reading the file—and I think saving it once—was enough to render it UNREADABLE for anyone running 10.6.6. Of course, if you download the file while you’re on 10.6.6, everything’s fine. Rather extraordinary, methinks...
Saving the file is the key part there. Just opening the file on 10.6.7 isn't going to change it. if you make some annotation or something, and re-save it, then it will be different. The system has to extract those embedded, compressed fonts in order to render the PDF. Then, after you edit and re-save, it will create the PDF with its own embedding and compression methods that are, alas, incompatible with anyone else is there are any OpenType Postscript fonts used.
In 10.6.7, you shouldn't create any PDFs that contain OpenType Postscript fonts. That also implies that you shouldn't edit or annotate them either. Anything you get from a source such as this one is always going to have Postscript fonts.
I will update my bug report to include the annotation problem (which I can easily reproduce). I won't do it until I get a chance to test on 10.6.6. Perhaps the fact that it also breaks under 10.6.6 will light a fire under someone at Apple.