You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Font problems after 10.6.7

I'm getting lots of strange behaviour relating to fonts since updating to 10.6.7. This is all in things that used to work perfectly.
PostScript output causes errors in Distiller (problems in font definitions); and manipulating PDF objects can cause embedded fonts to become .... unembedded.

As I understand it, there were lots of security fixes to font handling in the update, but it seems to have caused loads of trouble.

The developers for an app I use, Imposition Wizard, have confirmed that things aren't working as they are supposed to and have filed bug reports with Apple.

However, as I do a lot of work with PostScript and PDFs, I will have to reinstall the OS to 10.6.6.

iMac 2006 2Ghz, Mac OS X (10.6.7), MacBook 2008

Posted on Mar 22, 2011 3:07 PM

Reply
424 replies

Mar 28, 2011 8:18 AM in response to Kurt Lang

Kurt Lang wrote:
It will only seem that way until you run across an OpenType PostScript font that simply won't work. The bug (oddly) doesn't affect all of them.


I think it would be much odder if it did affect all OpenType PostScript fonts, since that would be just about impossible to miss during beta (or maybe even alpha) testing by both Apple & outside developers like Adobe.

I wish I knew more about the subject, but according to my limited understanding of it (here & in the following paragraphs), PDF is a subset of the Postscript programming language which does not support all the features of the PS superset but has become more popular because it is less resource intensive. Both support to slightly different degrees the features of the three principle font file formats in use today: Type 1, TrueType, & OpenType.

Type 1 is the only format that was developed exclusively by Adobe. Apple originally developed TrueType as a less expensive but compatible alternative to Type 1, licensed it to Microsoft, & both companies have extended their versions so there are two major variants. OpenType was jointly developed by Adobe & Microsoft, & is based partially on the MS TrueType variant (which in turn is based partially on Apple's original TrueType) & can roughly be considered a superset of the older formats, the main benefit of that being extended support in the PDF language for features otherwise only available in the Postscript language.

*In theory*, any Postscript or PDF interpreter, even older ones that don't know how to handle features of the newer OT font format, are supposed to be able to rasterize documents using any mix of the formats without problems by simply ignoring what they can't interpret, so while there may be small variations in the output of different ones there are not supposed to be any gross differences like missing characters or completely garbled pages, much less crashes or freezes.

Obviously, that isn't happening for everybody but I hope the above, as oversimplified as I'm sure it is, will provide some background info that might lead to better insights about why that is so.

Mar 28, 2011 8:45 AM in response to R C-R

That is a pretty accurate summary, R C-R. Good info for everyone to read.

The only thing we know for sure is that it is only OpenType PostScript that are goofed up in 10.6.7, and then only with PDF files created through OS X, and only when viewing them in Acrobat Pro or the Reader.

Beyond that, we can only guess where the fault is. It's very easy to say it's Apple's fault since there was no problem in 10.6.6 and earlier using the same fonts and methods. But like any other company or person, Adobe is not infallible. So it could be a long standing bug in Acrobat that doesn't conform to Adobe's own SDK on the PDF format, and now sticks out in PDF files created with OS X.

Though PDF files created directly from Adobe apps through the Distiller and in Quark 8 seem to disprove that. Such PDF files display fine in Acrobat under OS X, 10.6.7. And even that can be argued that Adobe and Quark just know how to work around an undocumented issue.

Mar 28, 2011 8:37 AM in response to benwiggy

Hello everybody. I got the same problem described by all of you. This little trick has worked like a charm for all the users in our company. We download a little app called Onyx (I'm sure everybody here knows it, but if not the case you can google). Then under the Cleaning Tab, run clear font cache (select all). Restart your Mac. Open any app you had the problem before (Flash CS5, Illustrator, etc). You'll see everything works perfectly.

Cheers.

Mar 28, 2011 9:07 AM in response to leozevallos

run clear font cache (select all). Restart your Mac. Open any app you had the problem before (Flash CS5, Illustrator, etc). You'll see everything works perfectly.


Cleaning the font cache may help Adobe PDF creation (from within Indesign, Illustrator etc), but this is not the problem here. This issues relates to PDFs created using the Apple 'Save as PDF' menu in the printer dialog or variants of it. Clearing the font caches was the first thing that I performed when this problem came up and it had no effect.

Mar 28, 2011 12:36 PM in response to SS_MedPhoto

I can confirm that saving PDFs from TextEdit and Word 2011, that contain OpenType PostScript fonts, through Apple's Printer Dialog, will result in PDFs that do not display well or even hang up Adobe Reader 10.0.2 or Acrobat Pro 9.4.3.

Fonts I tested were Adobe Minion Pro, Adobe Myriad Pro and Adobe Tekton Pro.

Interestingly, I get good results when creating PDFs using Pages '09.

Same fonts and apps on X.6.6 create usable PDF files.

Mar 28, 2011 3:15 PM in response to benwiggy

I updated to SN 10.6.7 last Friday. I did delete the font caches before I saw this thread, and as such, I have NOT been able to reproduce any of the problems in this thread. Since I saw info that there was a problem with 10.6.7 and OpenType PS fonts, I did several tests and have not run into any problems with PDFs in Acrobat, or with any output, so this could be related to font caches.

Mar 28, 2011 3:42 PM in response to benwiggy

Thanks to all for sharing. Good tips and thoughts abound.

We have two macs on Snow Lep 10.6.7 and BOTH can no longer use Word (Office Mac 2008) to make PDFs to send clients. Mac or PC, they hang in Reader and don't display, only a force quit gets out of it. Worked fine for years without a hitch. Then early last week, we upgraded to 10.6.7 and the issues began.

After blowing the weekend trying to solve this, I determined it had an issue with fonts, in particular OpenType fonts, but other fonts, too. Like Georgia. I can make all kinds of PDFs in Adobe Creative Suite CS5 with no problem. It's freaking Word (which my wife uses far more than I do). She needs this solved like: yesterday.

Considering a re-install of 10.6.6 on her current iMac. I can ride things out until the next update. So, I have no advice to offer, just posting so Apple will read this and come out with a fixer update asap. Thanks for reading.

Mar 28, 2011 3:53 PM in response to Kurt Lang

I'd agree that it's an OpenType PS issue as the problem appeared in printing in Quicken and then a test I did of several fonts using Pages. While Myriad prints, it's compressed and the letters are improperly formed. At first I was worried that my HP Laserjet 5000 was finally dying, but it did prove to be the fonts. The ONLY change was upgrading to 10.6.7.

Font problems after 10.6.7

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.