Currently Being ModeratedAug 10, 2012 10:21 AM (in response to hpr3)
hpr3: Thankyou, but preview does not recognize the files. All files appear as pdf, but simply can not be recognized by any other pdf program, nor word. Typical messages indicate, "not recognized", "damaged file", "no root", etc, etc.
Currently Being ModeratedAug 10, 2012 10:29 AM (in response to nmkijk)
This is strange. I do this all the time, and have never had an issue.
How are you saving them from Safari? Are you using an Adobe Reader plugin? Honestly, I'd remove that software from my machine entirely.
Currently Being ModeratedAug 14, 2012 8:42 AM (in response to nmkijk)
In OS 10.8 I couldn't open my PDFs, either, upon saving them in Safari 6.0. But by saving a 2nd time, the "PDF" notation disappears in the file icons and they show as images of the document itself, and open properly. Or save using the disk image in the gray bar as you roll over the bottom of the document.
Currently Being ModeratedAug 15, 2012 8:18 AM (in response to David A. Gatwood)
Try the following link:
Or - any online PDF file saved to the mac, either desktop, or download folder, etc. The link here is for an imac manual via apple.
Save in Saffari - the icon appears as an Adobe pdf file. When double clicking on the file to open, the following message appears; "There was an error opening this document. The root object is missing or invalid".
Currently Being ModeratedAug 15, 2012 10:24 AM (in response to nmkijk)
Here is what I observe when using the URL you gave.
1. It displays fine in Safari itself.
2. If I save it using the Save (the Diskette icon) in the Adobe viewer window within Safari, the saved file is fine
3. If I save it in Safari using Safari - i.e. File-> Save As then I get the "could not be opened" message in both Adobe reader and Preview
4. Examining the file save in step 3 above is is much smaller than the one saved in step 2 above - 20KB vs 4MB.
So at least for now save PDF's using the save function in the Adobe Viewer Window in Safari rather than Safari's save.
Currently Being ModeratedAug 15, 2012 11:34 AM (in response to Steve Holton)
I figured out what you did above, but I don't understand. Is there a difference between saving, and saving as? I have always saved as, which I cannot do unless I open the PDF in preview, and then save as. Also, you can save as by clicking on the action bar in the top right corner. It just seems very laborious to save something.
Currently Being ModeratedAug 16, 2012 9:08 AM (in response to nmkijk)
Easy, here's another option. Go to the link of the PDF and right click and choose "Download Linked File As.." and then type a name and choose location - presto. PDF's by default open in Preview. Furthermore, just install Adobe Reader for free from here: http://ardownload.adobe.com/pub/adobe/reader/mac/10.x/10.1.4/en_US/AdbeRdr1014_e n_US.dmg as the official Adobe reader has a lot more functionality and I prefer it personally.
Currently Being ModeratedAug 16, 2012 9:35 AM (in response to nmkijk)
Remove the Adobe plugin and uninstall Adobe Reader, Really QUIT Safari and restart Safari. Check in Safari Menu/Help/Installed Plugins that it is gone. This will solve the problem. You do not need Adobe Reader, Preview can do everything that is needed, and more. This issue also can surface in SnowLeopard and Lion.
Currently Being ModeratedJan 11, 2013 11:22 AM (in response to nmkijk)
Adobe Reader isn't my favorite, but neither are smug and uninformed assertions about Preview. There are PDFs that render only squares and marks under Preview (http://apple.stackexchange.com/questions/24209/this-pdf-displays-with-question-m arks-instead-of-letters), which is a common problem in MS Windows Office generated PDFs, so you may actually need Adobe Reader for Mac.
If you need to use Adobe Reader (as I do), then it may depend on the filesystem type where you save your PDF. For example, our Macs are network homed. Saving to desktop produced the error reported above no matter whether I used Safari:Save As, or the PDF save icon.
However, when I saved to a local drive (such as /tmp), then it worked. I don't know why file system makes a difference, unless Adobe is doing something with extended attributes that doesn't get written correctly to some filesystems.
Hope this helps.