in

Quark Forums

Zapf Dingbat problems with Leopard

Last post 03-17-2009 10:50 PM by tonz. 25 replies.
Page 1 of 2 (26 items) 1 2 Next >
Sort Posts: Previous Next
  • 04-04-2008 8:32 PM

    • LazDivaz
    • Top 500 Contributor
    • Joined on 05-28-2007
    • Playa Sámara, Guanacaste, Costa Rica
    • Posts 24

    Zapf Dingbat problems with Leopard

    Making revisions on a Quark 6.5 file. When I open the file, which had been created with Tiger OS, on my new mac, running Leopard, I get an alert that there is a missing font. Zapf Dingbats. I replace with Zapf Dingbats from the font pull-down list. The characters are then invisible in the file.
    What happened?
    Thanks for any help.
    www.lazdivaz.com
  • 04-09-2008 5:17 PM In reply to

    • automedia
    • Top 150 Contributor
      Male
    • Joined on 01-01-1970
    • Bournemouth UK
    • Posts 64

    Zapf Dingbat problems with Leopard

    Sounds like a Post Script problem - are you using a Font Manager? Some work others are best left well behind. Personally, I'd get rid of the Zingbats and then re-install them putting them in your >Users>Library>Fonts folder and try again. Bet it works!
  • 04-09-2008 5:41 PM In reply to

    • LazDivaz
    • Top 500 Contributor
    • Joined on 05-28-2007
    • Playa Sámara, Guanacaste, Costa Rica
    • Posts 24

    Zapf Dingbat problems with Leopard

    I am using Suitcase Fusion.
    I did what you recommended, disabled all fonts through Suitcase, and still, I do not see the characters in the Quark file. As I have a deadline, I'm working on my old Tiger system, and all is well. I'm convinced that it's a Leopard thing.
    I saw a note somewhere (can't remember where) that said that Leopard handles Zapf Dingbat in some strange way--UNIX coding, or some other thing that I don't understand.
    Anyway, thanks for trying to help.
    Sara
    P.S. The only font that works is the system font that comes with Leopard: ITCZapf Dingbats. As it is a True Type font, I can't use it for a live job.
    www.lazdivaz.com
  • 04-09-2008 6:31 PM In reply to

    • automedia
    • Top 150 Contributor
      Male
    • Joined on 01-01-1970
    • Bournemouth UK
    • Posts 64

    Zapf Dingbat problems with Leopard

    Hi - I don't agree that it's a Leopard thing - I use Leopard all the time but in 7.3.1 and I wouldn't have a problem using TTFs. In fact, I hardly ever have font problems. Try it and if it works, count your blessings!
  • 04-09-2008 6:36 PM In reply to

    • LazDivaz
    • Top 500 Contributor
    • Joined on 05-28-2007
    • Playa Sámara, Guanacaste, Costa Rica
    • Posts 24

    Zapf Dingbat problems with Leopard

    My client requires PostScript fonts for all projects. I agree, the Zapf Dingbats "dfont" appears on the screen and prints fine, but I just cannot use a TTF
    Why, if it is not a Leopard, does all work well with Tiger (same job, same file, same fonts)?
    That seems to rule out the Quark 6.5 issue.
    www.lazdivaz.com
  • 04-09-2008 7:00 PM In reply to

    • almaink
    • Top 25 Contributor
    • Joined on 06-02-2004
    • Lawrenceville, New Jersey
    • Posts 875

    Zapf Dingbat problems with Leopard

    LazDivaz:
    Making revisions on a Quark 6.5 file. When I open the file, which had been created with Tiger OS, on my new mac, running Leopard, I get an alert that there is a missing font. Zapf Dingbats. I replace with Zapf Dingbats from the font pull-down list. The characters are then invisible in the file.
    What happened?
    Thanks for any help.


    Leopard and system fonts is a little different than any of the previous OS's were.

    here is the poop on Leopard and fonts-
    In the past, pro font users tended to remove problematic system fonts such as Helvetica or Zapf Dingbats, because they tended to conflict with the users' own preferred fonts of the same name. These "required" system fonts were (and still are) stored in:

    /System/Library/Fonts

    In Tiger and earlier systems, you could delete such fonts by selecting, deleting, then authenticating as an admin. No problem (well, there were sometimes cache-related problems, but those were easily solved by adding back or enabling your own version of the deleted font, and before Tiger you probably had to clean the font cache as well).

    In Leopard, however, if you delete a "required" font like Helvetica this way, it will delete fine, but then you'll see a dialog that says "The system font 'Helvetica' was removed. This font file is required by Mac OS X to display onscreen text. It has been restored." And shazam, the font miraculously reappears in /System/Library/Fonts.

    So, NO WAY to get rid of such fonts? Not to worry, there's a solution:

    Navigate in the Finder (or your favorite file manager substitute) to:

    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/ProtectedFonts/

    Here you'll see a copy of key fonts needed by the system. Delete the font from this directory first, THEN you can delete it from the /System/Library/Fonts folder.

    You've essentially just broken Leopard's ability to repair itself as far as that particular font goes. But, in a pro publishing environment where your Helvetica is not the same as Apple's choice, that's something you sometimes have to do.

    As far as I know, the major font managers have not yet been updated to deal with this change.

    WARNING: don't try this at home if you're not sure what you're doing. This technique should only be used by experienced design/prepress users who simply MUST control their font destiny. If you remove Helvetica (for example) in this way, IMMEDIATELY replace it with the Helvetica of your choice PostScript, OpenType, TrueType -- but don't put it in the /System/Library/Fonts folder, instead put it in a higher-level place, like /Library/Fonts.

    And in NO case should you ever remove the Lucida Grande, Keyboard, LastResort fonts.
    Thanks to Chuck Weger at Printplanet for that one.
  • 04-09-2008 8:10 PM In reply to

    • LazDivaz
    • Top 500 Contributor
    • Joined on 05-28-2007
    • Playa Sámara, Guanacaste, Costa Rica
    • Posts 24

    Zapf Dingbat problems with Leopard

    Thanks so much, almaink, for the very clear explanation--I threw caution to the wind and went ahead with the process to eliminate protected fonts.
    I then put the PostScript font into the library, opened a Quark file, and, voilá--nothing!
    Here's something weird. I open Word, type 3 characters, style with Zapf Dingbats, perfect. I then copy these lovely characters, paste them into Quark, and see 3 question marks. I scroll through the font list, apply Zapf Dingbats, and get the invisible characters again.
    I'm going a bit crackers at this point, but I do believe that I have narrowed the problem down to QuarkXpress 6.52.
    What to do?
    www.lazdivaz.com
  • 04-10-2008 12:56 PM In reply to

    • almaink
    • Top 25 Contributor
    • Joined on 06-02-2004
    • Lawrenceville, New Jersey
    • Posts 875

    Zapf Dingbat problems with Leopard

    It could be you Quack font cache causing issues. If you don't already have it I recommend you download Linotype's free font manager. It has tool to clean out those pesky font caches.
    http://www.linotype.com/fontexplorerX
  • 04-10-2008 1:17 PM In reply to

    Zapf Dingbat problems with Leopard

    FontExplorer would wipe Suitcase Fusion on install.

    Use FontDoctor X Tools to clean your font caches. It came free with Fusion.

    or download Font Finagler.
    ... there was the puzzle of why the sun came out during the day, instead of at night when the light would come in useful.
    Terry Pratchet
  • 04-10-2008 1:23 PM In reply to

    • almaink
    • Top 25 Contributor
    • Joined on 06-02-2004
    • Lawrenceville, New Jersey
    • Posts 875

    Zapf Dingbat problems with Leopard

    Glenn McDowall:
    FontExplorer would wipe Suitcase Fusion on install.

    Use FontDoctor X Tools to clean your font caches. It came free with Fusion.

    or download Font Finagler.


    It would? If you set up Font Explorer to NOT manage your fonts it won't.
    Then you can use the tools in it.
    But ya Font Finagler is an option although it's no longer a free app.
  • 04-10-2008 1:48 PM In reply to

    Zapf Dingbat problems with Leopard

    I stand corrected :wink:
    ... there was the puzzle of why the sun came out during the day, instead of at night when the light would come in useful.
    Terry Pratchet
  • 04-10-2008 4:49 PM In reply to

    • LazDivaz
    • Top 500 Contributor
    • Joined on 05-28-2007
    • Playa Sámara, Guanacaste, Costa Rica
    • Posts 24

    Zapf Dingbat problems with Leopard

    Thanks, everyone, for trying to figure this one out. I have tried every suggestion you have offered, and then some: FontNuke, FontDoctor, Linotype FontExplorer X [what ever happened to word spaces?], all to no avail. The only viewable and printable Zapf Dingbats I can get are the True Type variety. Could it be that my Zapf is PostScript type 1? As is the fresh, clean, new font supplied directly by my client.

    Anybody wants to come and take care of this for me, you get a free night in my B&B! I give up, and I'm sticking with Tiger, which still works with Quark 6.52--I have a deadline!
    Cheers
    Sara
    www.lazdivaz.com
    www.lazdivaz.com
  • 04-12-2008 2:12 AM In reply to

    • LazDivaz
    • Top 500 Contributor
    • Joined on 05-28-2007
    • Playa Sámara, Guanacaste, Costa Rica
    • Posts 24

    Zapf Dingbat problems with Leopard

    Finally went to Quark online support today, determined to crack this sucker. After an hour of back-and-forth, clear-the cache, boot-in safe-mode and so on and so forth, the Quark tech finally admitted, "we don't see the Zapf Dingbats in 6.5, either; you have to upgrade to 7.1.3"
    The final word: Quark did not adapt 6.52 to suit the needs of the Leopards among us. If you want to run Quark in Leopard without a problem, you must upgrade to 7.
    As my client must have PostScript fonts, and must have 6.52 files, I have to work in Tiger. Full stop. The end. InDesign, here I come! Quack!
    Thanks, one and all. The offer for a free night in my B&B is hereby retracted, owing to the impossibility of the qualifying mission.
    Goodnight, Mrs. Calabash, wherever you are!
    www.lazdivaz.com
  • 04-12-2008 8:38 PM In reply to

    • almaink
    • Top 25 Contributor
    • Joined on 06-02-2004
    • Lawrenceville, New Jersey
    • Posts 875

    Zapf Dingbat problems with Leopard

    No idea why your client is insisting on postscript fonts. There is nothing wrong with using True Type fonts as long as they come from a reputable place. True Type fonts got a bad rap years ago and the stigma is still with them today unfortunately and unfairly. I know that doesn't solve your problem but I get sick of True Type getting a bad rap and I use them all the time with no issues.
  • 04-12-2008 9:01 PM In reply to

    • LazDivaz
    • Top 500 Contributor
    • Joined on 05-28-2007
    • Playa Sámara, Guanacaste, Costa Rica
    • Posts 24

    Zapf Dingbat problems with Leopard

    I do not have an issue with True Type fonts. I also use them all the time without a problem. The issue is that Quark has no interest in troubleshooting what they have finally acknowledged is a problem with 6.52 vs. Leopard. Their solution, in the hideous greed-driven marketplace, is to help me out by telling me to spend $300 to upgrade to their new product. They really don't give a damn about fixing a bug.
    Anyway, my job is live, I have to finish it in 6.52 with Tiger, and I can stop wasting my time trying to find a solution to a problem to which there is none.
    www.lazdivaz.com
Page 1 of 2 (26 items) 1 2 Next >
Powered by Community Server (Commercial Edition), by Telligent Systems