Leopard and CS3 and Quark and more...

[wonderings]

Hi all, just wondering how things are working for those who have installed Leopard. Any issues with CS3 or Quark? Printing or network issues?

thanks

[SlaveToTheMan]

Not installing Leopard on production machines any time soon, there are NO real worl dbenfits that I've seen so far to warrant the risk.

That being said, I'd love to hear tales from anybody who has taken the plunge!

[wonderings]

I wouldnt do it on the main machine. I always test new versions of the software we use on my machine first before installing it on my co-workers machine which is the main production computer. I think I am going to give it a go today when I have cleared a few jobs away.

[Cory Smith]

I haven't tested it myself, but there have been a few articles on macnn about compatibility

http://www.macnn.com/articles/07/11/...ss.73.leopard/
http://www.macnn.com/articles/07/10/...ps.on.leopard/

[almaink]

One major issue is keeping me from upgrading and it's fonts. Seems the Helvetica dFont in system/library/fonts can no longer be replaced with a type 1 version. If you play with the preferences in Font Book that is turn off auto activation and the font warning you can remove the font but it still re-spawns as soon as you close the font folder. No way can I have two versions of helvetica active at once.

[cweger]

Here's a post I just sent to MacInTouch that should help with the boomeranging Helvetica problem:

There's a new font-related feature in Leopard that's probably excellent for consumers and business users, but might cause pro design/prepress people some problems:

In the past, pro font users tended to remove problematic system fonts such as Helvetica, 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.

Hope this helps others who battle with fonts daily.

[almaink]

Nice fix Chuck! I knew someone would find an answer for this annoying issue.
Thanks!

[disbellj]

Chuck,

I'm keeping that post around for when I get Leopard in the house. Great post!

Have you seen any problems with running Quark 6.5 and Adobe CS2 with Rosetta in Tiger or Leopard (that's not been fixed with updates to the programs or OS), or running Quark 7.3 and Adobe CS3 native in Tiger or Leopard (that's not been fixed with updates to the programs or OS)?

I'm coming from a PPC G4 Dual 500 MHz and getting a Mac Pro. Just curious (and needing to know what to look out for in particular) about these programs and their problems (if any) on Tiger and Leopard on Intel Mac. I'll get Sheep Shaver if I have to.

Much thanks to you!

Don

[Bobmorli]

After 2 days of 'testing' leopard on an intel mac, I went back to tiger.

The helvetica issue which Chuck solved now was one of the problems.


Another major problem was network and conections to windows servers. Once connected to servers, there was a 50% chance I couldn't see any items inside a folder; wasn't able to edit files and save them. Tried AFP / SMB / CIFS but nothing really gave a good way of working. Since I didn't find any good help on the net, I went back to Tiger on the production machine.
Meanwhile I've installed Leopard on another testing mac (G4 dual 1,42). First test also gave me network problems. So now IT is looking into the matter because at home I haven't come across any problems with the network (windows server 2003 and powerbook G4 with leopard).

Quark 7.3 seems to run nicely, haven't yet had any problems with that. Photoshop and Indesign run faster but Illustrator seems to go into a loop or something if I open more than 6 files. The CS2 does that without a problem. And Acrobat 8 is slow in general.

[disbellj]

So no problems with Adobe or Quark on Intel Mac (e.g. Mac Pro) running Tiger? If those problems have gotten worked out, then I could at least run Tiger and run CS2 and CS3 and Quark 6.5 and Quark 7.3. I could then install VMware to run Windows stuff (and maybe Leopard too for testing), and install SheepShaver to run what I run in Classic now (OS9 and it's apps PageMaker, Preps, and maybe Quark 5). Just wanting to move to one machine and am willing to test it, just looking for heads up from anybody that's already done any of these to see potential problems and if any of them haven't been fixed with updates.

Don