Font problems after 10.6.7

Sorry, i am pretty frustrated with Apple, not with anyone here personally.

I picked up the iMac today finally and i'll give the downgrade a shot. Thanks for the really detailed help mate, i thought that might be the case with the laptop.

Yes, This is definitely not an option for us as our software depends on a few of these fonts, I can replicate the issue shown at this link
http://kb2.adobe.com/cps/896/cpsid_89637.html

Thanks for that link, Hyperblaster. I'm encouraged somewhat by the "Solution" on the page..."Adobe is currently working with Apple to provide a permanent solution for Mac OS X 10.6.7+"

That's the first official acknowledgement I've seen from either party that this problem even exists.

Hi R C-R,

but I've lost track of who said what.

Haha! Yes, I find myself looking back through posts to try and remember who said what.

Pretty much all of your questions are answered here:

http://discussions.apple.com/thread.jspa?messageID=13295716#13295716

I did only test the latest version of the Acrobat Reader. I wanted to keep the test drive as much of an OS X install only as possible. But I think the results were conclusive. All fonts work in 10.6.6 using the methods OS X allows in its menus. Which are really just "Save as PDF" and "Save as PDF-X". I could open the PDF files in Preview or Acrobat with no issue no matter what fonts were used. As soon as I installed 10.6.7, Acrobat could not open PDF files containing OT PS fonts.

That is specific to 10.6.7. PDF files I created in 10.6.7 with OT PS fonts could not be read by Acrobat. But PDF files created under 10.6.6 with the same fonts could still be read.

schmidhauser wrote:
A precision: it wasn't me who created the PDF but an author who goes by the name "u674" (presumably one of people at the Press); and Adobe InDesign CS2 (4.0), which is specified as the Content Creator, was running on his or her machine.

But you are the author, correct? I would like to submit this document to Apple with your permission.

It does indeed fail to open in Preview on 10.6.6. Even though it was created by InDesign, I suspect it uses the new 10.6.7 routines to compress the embedded fonts. That is one of the things that causes problems for Acrobat Reader. I don't know why Preview in 10.6.6 has problems. This is new. Perhaps that version of Preview is using Adobe code and Apple switched to their own code in 10.6.7. It will open with Preview in 10.6.7 and it will open with FoxIt for Windows. Still, Apple has made the Portable Document Format distinctly non-portable.

I can't open that PDF file under 10.6.6 in Preview or Acrobat, either. Hangs both of them.

schmidhauser,

How was that PDF saved out of InDesign? Through File > Adobe PDF Presets > option, or just the Print command?

I'm late to this discussion, I know. I'm wondering if my problem is related to what's going on here. Using Acrobat Pro 9.4.3 I can print a document to my Canon iPF8000 wide format printer but none of the type prints out. In other words, images print fine but all font/type content is missing. Fonts display on screen OK in PDF documents generated from InDesign CS4's own internal Export>PDF function. And yes, I have downloaded and installed the latest print driver from Canon after proper deinstallation of the extant driver. Nothing has changed on my system except the 10.6.7 update and everything was dandy before that... Any ideas folks?

Hi Simon,

Yes, if you have OpenType PostScript fonts in the document you're printing, it's related.

Not so fast. See this: http://discussions.apple.com/message.jspa?messageID=13355208#13355208

I couldn't print a one-line PDF containing only the text "This is a test of Times" in TrueType times font from a 10.6.7 machine to one specific Canon printer shared by another 10.6.7 machine.

I give up. This 10.6.7 issue is making me look like an idiot. The only fix is to roll back to 10.6.6.

This is driving me nuts. I deleted the printer and re-added it and now I can print fine.

This is driving me nuts.

And everyone else. 🙂 It's an ugly situation. They can't get it fixed fast enough, whoever takes charge on this.

I'm going to go back and hide in the "MacOS X Technologies" forum until 10.6.8 comes out.

I'm going to go back and hide in the "MacOS X Technologies" forum until 10.6.8 comes out.

Nah! You help a lot of folks out. Keep pluggin' away.

This whole mess is really bad for people buying new Macs. There is someone in these threads who bought a new MacBook Pro to use rather than trying to downgrade the Mac he had. The new Mac came with 10.6.7! No recourse on that one at all, or for anyone else getting a Mac shipped with 10.6.7. They have no choice but to wait for a fix.

@etresoft & @Kurt Lang

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/

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...