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 31, 2011 5:54 AM in response to powerbook1701

Also, what is the Myriad Pro font? Is that a preinstalled font by SL?


No, it is not pre-installed. It is a commonly used Adobe font, which has been packaged with various CS products over the years as part of the registration free gift or alternatively that has been bought from Adobe.

see http://store2.adobe.com/cfusion/store/html/index.cfm?store=OLS-UK&event=displayF ontPackage&code=1706

Mar 31, 2011 10:25 AM in response to Steve Werner

I'm an IT Manager at a design firm and the 10.6.7 update is causing havoc. Is there a workaround? Our account managers use Adobe Pro 9.2 to create and edit Microsoft office doc(x)s converted to pdf's.
Our templates use open type fonts (branding, replacing font not an option). Rolling back to 10.6.6 is killer unless there's a time machine backup. Anyone?

Mar 31, 2011 10:55 AM in response to powerbook1701

powerbook1701 wrote:
well, since Apple just addressed the whole MacBook Air and iTunes freezing issue, one would hope a fix for this is just around the corner.

Also, what is the Myriad Pro font? Is that a preinstalled font by SL?


I wonder when someone asks me what's the Myriad Pro font 😀

Adobe's Myriad Pro (that's the full name) is the font that Apple use in many products: for example, if you get an iPod or an iPhone and analyze what font is used to write "iPhone" or "iPod" in the back... well, that's Myriad Pro.

So, it's very curious to see that even this font gets messed up with SL 10.6.7 .

I have feedbacked this issue to Apple, hoping that they will fix it soon.

=== PLEASE NOTE: UPDATE ===

Pages, in my machine, IS NOT affected by the issue: I have printed a document written in Myriad, Helvetica Neue and Courier New some minutes ago with BEST results: ALL, I say ALL, fonts are fully readable and don't get messed up.

So, I would recommend using Apple's Pages. OpenOffice 3.2.1 and 3.3 don't work for me.

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

SS_MedPhoto wrote:
It is a commonly used Adobe font …


But as the link makes obvious, it is actually a font family of 10 related typefaces, each in its own file, & not all of them might be installed. A little less obvious, like many other fonts (OpenType or otherwise) over the years slightly different versions have been released, so not everyone that has the Myriad Pro font installed necessarily has the same sets of glyphs in those files.

Much less obvious (at least to me), OpenType is not exactly the fully platform & application independent font technology I once thought it was. I don't know that much about it, but after wading through Adobe's OpenType® User Guide for Adobe® Fonts pdf file, I'm kind of amazed there are not more problems related to platform & application differences. Apparently, not even all of Adobe's apps handle OpenType exactly the same, & there are a fair number of quirks that can develop when a document is created on one platform & viewed on another unless special precautions are taken.

I have no idea if this has anything to do with the 10.6.7 problems, though. Maybe some font expert can shed some light on this …. ?

Mar 31, 2011 1:02 PM in response to curtsmedia

As curtsmedia said, you just have to convert the fonts to ttf, because the problem is with otf fonts, there is no need to roll back your OS, just erase your Myriad Pro font and install the new one.

I've converted my fonts and it's workin fine, if you like you can downlod the Myriad Pro family from here

https://www.yousendit.com/download/UFh1aklqaytqY3J2Wmc9PQ

Mar 31, 2011 1:03 PM in response to James Shea1

The 1st machine I rolled back to 10.6.6. using the SL disc worked fine, it was the 2nd that got through phase 1 and then rebooted and hung. Yes, i repaired permissions before the rollback. I had to eject the disk and restore from TM. I got lucky though cause not all users are backed up with TM. This is crazy, Adobe or Apple needs to come up with a patch.

Apr 1, 2011 1:19 PM in response to curtsmedia

The online www.freefontconverter.com tool also cleared up the font problem for us. Our workflow is such that we have two OS X 10.6.7 systems with a LOT of OpenType fonts on them; perhaps about twenty different font families and over a hundred .otf files overall. But the majority of our systems only have one or two OpenType fonts on them -- HypatiaSansPro and OptimaNovaLTPro. I simply took these two fonts (eleven .otf files overall), ran them through www.freefontconverter.com to create TrueType (.ttf) equivalents in under ten minutes, and am replacing the OpenType versions with TrueType on our systems.

We’re still figuring out how to best handle the two design systems with the large number of OpenType fonts, but if you have a small number of fonts giving you troubles, it seems much easier to convert them to TrueType than downgrade to OS X 10.6.7. If you have hundreds or thousands of OpenType fonts then of course the conversion may not be the best approach for you. Your milage may vary!!

Note that in addition to the www.freefontconverter.com tool, a couple of other free online conversion tools are described at http://www.ehow.com/how6366601convert-type-true-type-font.html and also the TransType Pro conversion tool ($179 -- see http://www.fontlab.com/font-converter/transtype/) seems like it might be a useful product, but I have no experience with it.

Hope this info helps!!

Apr 2, 2011 7:33 PM in response to benwiggy

A strange variant on the font problem:

I loaded a Photoshop file I handn't used for a while. It wanted to substitute a font for 'Lucida Handwriting'.

Font Book shows it to be present, but Linotype Fontexplorer says it's absent.

I found a reasonable substitute on line - 'Chopinscript'. Downloaded and installed it, and...

Font Book says it's present, Fontexplorer says not.

Wrod sees it, but Photoshop doesn't.

Er...

I'm lost. Can anybody suggest a course of action?

Thank you.

Apr 3, 2011 8:20 AM in response to Hillcrest

Font Book says it's present, Fontexplorer says not.


The gist of the problem is right there. You should never have more than one font manager on your computer at a time. Assuming FEX is the one you prefer to use, you need to completely remove Font Book.

To remove Font Book from the hard drive, follow these steps:

1) Open Font Book, and then its preferences. Uncheck the box for "Alert me if system fonts change". Close the preferences and shut down Font Book. Put the Font Book application in the trash and delete it.

2) Restart your Mac and immediately hold down the Shift key when you hear the startup chime to boot into Safe Mode. Keep holding it until OS X asks you to log in (you will get this screen on a Safe Mode boot even if your Mac is set to automatically log in). Let the Mac finish booting to the desktop and then restart normally.

This will reset Font Book's database and clear the cache files in your user account. Any font sets you have created will be gone. Also, all fonts in the three main Fonts folders (System, Library, your user account) will now be active, regardless of their state beforehand. Not that what happens to Font Book's sets matter. We're removing it.

The main goal for the Safe Mode startup is to remove the orphaned Font Book database from the hard drive. With the Font Book application no longer on the hard drive, a new one cannot be created. Which is what we want.

3) Close all running applications. From an administrator account, open the Terminal app and enter the following command. You can also copy/paste it from here into the Terminal window:

sudo atsutil databases -remove

This removes all font cache files. Both for the system and all user font cache files. After running the command, close Terminal and immediately restart your Mac.

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.