Q: Font problems after 10.6.7

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.

This issue shows up in Final Cut Pro under the Boris Title 3D tool - which means that all of the text in one of my edited sequences is now corrupted. Hope Apple fixes this soon. I have rebooted to a backup if 10.6.6 and the issue disappears.

Does this issue affect the displaying of text (with Adobe fonts) in Final Cut Pro 7? I opened the same project file using my MBP (10.6.7) and iMac (10.6.6) and the text showed up on my iMac only.

I have similar problems to everyone else. Open Type fonts don't show up or act screwy.

I wanna add my voice to the crowd. Apple we need you to fix this and quickly.

I'm a designer and use these things to make a living. I don't have the time to backtrack to 10.6.6.

We'd appreciate some acknowledgement of the issue and to know that you are working on it.

we can confirm, this issue appears while using apples internal system libraries for creating pdfs with open type fonts. trying postscript files on distiller cancels the job with error on font stack. saving as pdf makes unreadable output and error message on reading the embedded font.

since this is an unacceptable situation for all design studios around the world, apple should be encouraged to fix this problem within the next view hours. this issue has blown up or meeting yesterday with an important customer. pushing this issue to adobes fault is not an option. seriously, advising to downgrade also is not an option.

kind regards from germany

since this is an unacceptable situation for all design studios around the world, apple should be encouraged to fix this problem within the next view hours. this issue has blown up or meeting yesterday with an important customer. pushing this issue to adobes fault is not an option. seriously, advising to downgrade also is not an option.

I wouldn't be overly optimistic that there will be a speedy fix. This problem seems to have completely passed many builds in beta testing and may take a little time to sort out.

The good news is that downgrading with 10.6 is less problematic than with previous versions of Mac OS X as applications and user folders are left intact and useable (better than the old archive and install) and the installer doesn't refuse to work because the system on the computer is newer than that which is being installed.

Just remember to deauthorise all those Adobe CS applications before you start, or you'll be phoning Adobe before you finish!

Jayfsee wrote:
I wanna add my voice to the crowd. Apple we need you to fix this and quickly.
{…} We'd appreciate some acknowledgement of the issue and to know that you are working on it.

Please note that Discussions is a user-to-user forum. You are not talking to Apple here, just to other users. And as explained in the Terms of Use Apple does not provide any formal technical support here, nor would any information that it or its employees post here informally come with any warranties of any kind.

If you want to contact Apple about this, try http://www.apple.com/feedback/macosx.html. Be sure to describe the problem in detail. (Not everyone has the same problems.)

Most people are rolling back to 10.6.6, it will resolve the problem.
But not everyone has that option, as you can see from my first post here: http://forums.adobe.com/thread/825673, I was running 10.6.6. The newest MacBooks are delivered with a newer build & kernel, so I cannot roll back, can't use my new MacBook Pro right now. :'(

Logic interface wrote:
Most people are rolling back to 10.6.6

How do you know what most people are doing? There are millions of Snow Leopard users around the world. How many did you consult before coming to this conclusion?

I haven't been able to figure that one out. A few folks, like yourself, have noted that just clearing the font cache files fixed the problem.

But I've tried that, multiple times, as have other here without any change in the problem.

Are you using OpenType PostScript fonts? OpenType TrueType will not cause the issue. And even more confusing, an OpenType font ending in .otf is not necessarily a PostScript version.

R C-R wrote:

How do you know what most people are doing? There are millions of Snow Leopard users around the world. How many did you consult before coming to this conclusion?

I lol'ed! I'm guessing it's not affecting your daily workflow, but maybe you could try to sympathize instead? With 'most people', I mean those that are affected. And obviously I can only extrapolate what's going on in our business… Imagine the next update killing your audio setup, what would you do? I can't roll back, as explained in my post. But I'm using my old MacBook Pro instead… that's almost the same as rolling back, no?

Message was edited by: Logic interface

Logic interface wrote:
With 'most people', I mean those that are affected. And obviously I can only extrapolate what's going on in our business… Imagine the next update killing your audio setup, what would you do?

If your livelihood depends on your computers, then you have to be very careful about updates. People have gotten into a security paranoia and feel that if they don't update TODAY they will be hacked and their machines turned into hacker-serving bots before lunch time. Having some sort of OS bug or 3rd party software incompatibility is far more likely.

That being said, this bug really shouldn't affect professionals at all. They should be running Acrobat, InDesign, Quark, etc. This bug should only affect casual users who have installed Adobe Reader (even though they didn't need to), created documents using those fancy Adobe fonts, and then distributed those PDFs. Such users just need to disable those OpenType Postscript fonts and wait for a fix. Your only loss is a few fonts.

Such users just need to disable those OpenType Postscript fonts and wait for a fix. Your only loss is a few fonts.

Far more than a few, I'm afraid. For those who work from Adobe's Font Folio 10 or 11, all of the fonts are OpenType PostScript. Linotype's latest font folios are also completely OpenType PostScript.

Full press and prepress shops also must remain at 10.6.6 to be sure they can print to their PostScript printers and RIPs, as you can never be sure what type of fonts a client will send you with their project.

So has anybody seriously considered the possibility that it is just certain OpenType Postscript fonts that cause these problems, or just certain typeface styles that might not be included in every distribution of those fonts?

Could it be that this is why some users are seeing substantially different problems from others or why some fix that works for some don't for others?

i am reading some of the last responses only with a shake of the head. guess you are not faced with the problem at all. you are talking about adobe apps, but what about all the other tools, using apples system library for creating pdfs, what about a corporate font you have to use and are unable to, because your system is broken - broken by an update delivered by the manufacturer.

i would like to see you in action, when you collect your car from the dealers garage, realizing engine trouble because of a broken software update.