Apple’s Worldwide Developers Conference to kick off June 10 at 10 a.m. PDT with Keynote address

The Keynote will be available to stream on apple.com, the Apple Developer app, the Apple TV app, and the Apple YouTube channel. On-demand playback will be available after the conclusion of the stream.

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

Apr 27, 2011 6:15 AM in response to mijägo

Shame on Apple for being incapable to communicate that problem with their customers.

Hardly "incapable". That suggests they can't speak, write, or otherwise tell others what they can or cannot do.


Anyone who's been using Apple products long enough knows that this is their normal mode of operation. They very rarely respond publicly to complaints about their products.

Apr 27, 2011 6:16 AM in response to Nick Hobart

It's very important to understand that this forum is for user-to-user support.


It is not nor was it ever intended to be a channel for reporting problems to Apple.

For that you should contact Apple support, your SE (if your company has one),

and bugreport.apple.com - and when filing a bug report, please make certain to read

http://www.afp548.com/article.php?story=20051102133234150


As for Apple commenting on a problem, their established policy is that they don't,

until such time as they provide an official update. You should expect the same of other large companies,

anything to the contrary is most probably non-official statements of one sort or another.


It's not my intent to debate any other statements about Apple.

Apr 27, 2011 7:15 AM in response to mijägo

mijägo wrote:


...and who ever said that Apple do not listen. Shame on you.

Shame on Apple for being incapable to communicate that problem with their customers. I wonder how people can defend such a lack of sensibility and accuse the people who are annoyed by Apple's behaviour. This criticism does not exlcde the fact that I am grateful that finally Apple has released a functioning update and that faults can happen. IT IS THE WAY HOW Apple dealt with this issue which I criticise. I hope Apple finds a better way in the future. Communication and customer friendly behaviour seems to be a weakness of Apple, I wish this is going to be improved in the future.


(This point does also not ecxlude the fact, that I am a grateful user of a MacBook Pro and its operating system which is really an excellent product. With respect to this I wish to express my gratefulness und respect for all the hard workers, designers and engeneers of Apple. )


<Edited by Host>


Those of who are long term Apple users such as Kurt and David Lang would get that my comment was for humour. All of us know Apple never comment. I have been using Apple since '86 even though the new communities wiped my log ins ( yippee.. being sarky there ) and so my log in says only a few days ago.


I have never heard from anyone that has had an apology or personally seen one or seen a problem admitted in the past 25 years.

I am talking about hardware here and not the iPhone 4...

Apr 27, 2011 8:02 AM in response to Kurt Lang

Hardly "incapable". That suggests they can't speak, write, or otherwise tell others what they can or cannot do.


Anyone who's been using Apple products long enough knows that this is their normal mode of operation. They very rarely respond publicly to complaints about their products.


Yes, the term is too strong - I am not a native speaker. Sorry for that.


It seems most of the Apple users accept that behaviour.


<Edited by Host>

Apr 27, 2011 7:22 AM in response to davidh

As for Apple commenting on a problem, their established policy is that they don't,

until such time as they provide an official update. You should expect the same of other large companies,

anything to the contrary is most probably non-official statements of one sort or another.


I like the Adobe way, they addressed the issue in a short note:

http://kb2.adobe.com/cps/896/cpsid_89637.html


and the said:

"Adobe is currently working with Apple to provide a permanent solution for Mac OS X 10.6.7+. In the meantime, you can downgrade to Mac OS X 10.6.6. You can find the install at Apple's support site."


I see this approach as reasonable and customer friendly.

Apr 27, 2011 7:29 AM in response to mijägo

I am not a native speaker.

Kind of wondered that. Explains the misuse of "incapable".

It seems most of the Apple users accept that behaviour.

That's pretty common behavior in lots of companies. I've brought my Toyota in for an oil change a few times, and on two of those, was informed that there was a minor recall issue to fix as long as it was there. That I've heard of, all car companies do this. Unless it's a major recall, you don't here about it until you bring your vehicle into the dealer for other service.


That's basically what happened here. The font issue was an ugly bug, but, it's not like there wasn't a way around the problem until an official fix was released. Reinstalling the OS and updating only as far as 10.6.6 wasn't fun to do (especially if you had multiple machines), but it could be done to get you back to a working state. The only people who were truly stuck were the small percentage with brand new Macs that came with 10.6.7.

Apr 27, 2011 9:32 AM in response to benwiggy

I am having font problems as well.


I already had 10.6.7 when I bought a Brother MFC-9970CDW (killer printer btw). I started printing and noticed that on some PDF, DOC and DOCX files the fonts would get stretched vertically to oblivion, they looked like barcodes.


The issue only seemed to happen with fonts that had been bolded or italicized but I couldn't distinguish a specific pattern. I think this is the same issue you guys are describing.


Printing from MS Word, Preview and other apps didn't change the problem. However, when I loaded the documents on to a USB stick, plugged that in to the printer and printed directly from the USB key, the issue seemed to disappear. I also noticed that printing from USB resulted in better contrast and there weren't any issues with page margins getting cut off either.

Apr 27, 2011 12:56 PM in response to Kurt Lang

in case anyone's curious, it looks like these are the files included in the font update:


Info.plist

libFontParser.dylib

libTrueTypeScaler.dylib

libType1Scaler.dylib

version.plist


all in the directory:

/system/library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/A TS.framework/Versions/A/Resources/


also, it looks like they were last changed on 4/18 and 4/19.

Apr 30, 2011 12:22 PM in response to benwiggy

To those of you who applied my fix package, you will need to reinstall the

10.6.7 update package first or manually reinstall the 10.6.7 ATS.framework

files before installing Apple's Snow Leopard Font Update.


----------

To manually reinstall the ATS.framework files:

Download the MacOSXUpd10.6.7.dmg (10.6.7 update) from Apple.

Mount the MacOSXUpd10.6.7.dmg and open the MacOSXUpd10.6.7.pkg

with Pacifist.


With Pacifist, Restore the following bundle:

/System/Library/Frameworks/ApplicationServices.framework/Versions/A

/Frameworks/ATS.framework.


Now download and apply Apple's Snow Leopard Font Update.


Kj

Apr 30, 2011 1:27 PM in response to KJK555

Thank you Kj for this instruction.


When the Apple update was announced I downloaded the 10.6.7 combo update and I installed it to avoid possible problems with your bug fix. Then I downloaded and installed the official Apple font bug fix. There was no problem to apply this procedure.


Your bug fix was a great help, thank you very much again!

Apr 30, 2011 4:38 PM in response to C42D

Thanks to all who tried to resolve the problem, but for me, the bug fix did not work. (nor did clearing the font cashe, etc.) MS Office aps do not recognize some of the otfs like Warnock Pro, while they recognize others, like Myriad Pro. Both of these are required for some of the work I do, so I'm still seeking a soluton.

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