Font Issues with iWorks and OS Mountain Lion

Not sure that I want to upgrade to Maverick yet but thanks for the suggestion.

Well I made some progress with solving some Pages 09 problems with fonts without having to resort to Maverick (yet). This morning I had five fonts from the Myriad Pro family which produced only gibberish, now I only have one font that has a problem "Myriad Pro Light Italic" which is missing from FontExplorer listing, exist elsewhere on my system but will not copy and paste to FontExplorer because it says that it is already in their database. Can't see where it is.

Andre

How old are those fonts?

Are they .otf? or Postscript type 1?

Peter

Hi Peter, those are all open type .otf fonts, probably all very recent, 2010 perhaps. The same fonts that I had before Pages started acting up as I've described. Ten days ago everything was fine. Come to think of, it I upgraded, FontExplorer a few days ago ... so that might have something to do with it. I tested TextEdit again and it doesn't have the problem that Pages has.

Andre

ElZitouni wrote:

Hi andre244: the solution to this dreadful problem is -- clean install Mavericks. Granted, clean install is not necessary to resolve the font issue, Mavericks will do that by itself. However, I have done an upgrade install kind of thing and my MacBook Pro slowed down to a crawl. That sluggishness completely disappeared when I succumbed to a clean install.

ANYWAYS: you can rejoice, because all these idiotic font issues disappeared with Mavericks, both in the newest versions of Keynote et al, as well as in iWork9.x.

Good luck!

ElZitouni.

You are typically associating what may be coincidental or non-primary results with what has actually happened.

A lot of things are left behind and/or removed in a clean install. That does not make a clean install the solution except as a blow-it-all-up, start again solution. Possibly reinstalling a clean version of Mountain Lion would have done the same.

As I said before it smells of font/font cache problems. Both can be tackled in Font Book, one by isolating and removing problem fonts, two by recreating the font caches.

Peter

Dear andre244: just to be as clear as possible regarding my postscript Futura font problem:

1. the problem started when I upgraded from 10.7 to 10.8, and disappeared when i went to 10.9.

2. the problem did not disappear because of a clean install because it disappeared already without a clean install -- i clean installed after a normal install because my computer got to slow and the clean install solved that. but the font problem was solved with a normal install.

3. i tried everything possible, removing and re-installing fonts, clearing the font caches, removing and reinstalling iWork, etc etc etc etc. Nothing solved this problem.

4. it was isolated to some faces of my futura post script font, and to iWork.

I personally liked Maverick, so for me that was all around a good outcome. For you that might not work.

Best of luck,

ElZitouni.

Peter, please give other people here the benefit of the doubt but, more importantly, try to read their eMails before commenting.

As I stated before, and for you I say it again: the problems with the postscript Futura in iWork disappeared with a standard install of Mavericks. The clean install was not necessary to resolve the font issue. The clean install was done weeks after the standard install in order to speed up the machine, which worked.

As for the font issues: my font problem came after installing 10.8. It was not present in 10.7. And nothing could solve it, contrary to your insinuations, and I have tried it all. Whether this is exactly the problem that andre244 faces, I don't know. Perhaps not, it may be a different type of problem, the one you suspect at the root perhaps.

ElZitouni.

Hello ElZitouni,

I've been in 10.8 for well over a year and had no problem with Pages "turning text into gibberish", so I'm not sure that Mountain Lion has anything to do with it.

I'm wondering if *my* problem is not my having upgraded the new version of FontExplorer X Pro version 4.1 (build 9356). The "problem" and my upgrading have happened during the same period of time (past two weeks).

I'm glad to hear that a clean-install was not essential to solving your problems with Pages, but on the other hand the slowing down of your system after an upgrade is something worth looking into.

I understand your points 3. and 4. because that is exactly what I also went through but now I'm happy to report that **all** my Myriad fonts are working fine with Pages. The solution was to de-activate some fonts from: [ /Mac Hd /Library /Fonts ] and re-activating these same fonts into: [ /Mac HD /Users /"me" / FontExplorer /Font Library ]. None of these de-activating/re-activating operations made any sense to me but I simply followed FontExplorer's suggestions and voilà everything is back to normal.

Andre

Hi Andre: great that it worked out this way! For unknown reasons, this approach did not work with the bizarre Futura problem I had for a long time.

As for the speed increase in Mavericks after a clean install -- I did this after I read in some forums that it helped others that faced a similar strange slowing down of Mavericks. Perhaps Apple's upgrade install algorithm for Mavericks is faulty and leaves too many outdated redundancies around. Who knows ...

Best,

ElZItouni.

ElZitouni wrote:

…and I have tried it all.

…and I have heard that many times here.

What the user means is they have tried everything they can think of or presuppose.

Then we get down to the real solution, once we get past the unlucky guesses and actually look at the problem rationally.

Peter

Hi Peter, I agree with "What the user means is they have tried everything they can think of or presuppose."

I'm trying to look at the problem rationally: I've solved the problems that Pages had with Myriad. I did that by shuffling fonts around but could not see anything logical about what I did... BUT it did solve the problems. With Myriad !

NOW Pages has the same problems with Museo and since there was no logic in how I solved Myriad ( but spent hours on it) I'm not sure that I can keep solving all the problems that Pages has.

"Rationally" I'm comparing Pages with TextEdit and Scrivener, these last two never showed **any** of the problems that Pages had ... so I can only logically conclude that the problem is with Pages.

That's all I can think of or presuppose ...

Andre