Any Mac Folk Updated to Lion - Issues?

bojev's picture

Thinking about updating from Mac OS 10.6.8 to Lion at some point - has anyone tried this and what problems and issues have you encountered. Especially interested in Adobe Creative Suite, FontLab and Fontographer.

dezcom's picture

I have no problems with Lion.

bojev's picture

Thanks Chris, That is encouraging.

eliason's picture

What version of FontLab are you currently using?

bojev's picture

FontLab Studio 5.1

eliason's picture

Okay. If you were a 5.0 holdout I'd warn you that it doesn't work in Lion and there are some lingering bugs yet in 5.1, but as you're using it already you know what you're in for.

Thomas Phinney's picture

I've heard some rumblings about network issues on Lion from our IT folks. They have to deal because new Macs come with Lion, but they do not recommend anybody else in the company upgrade yet, unless they have to for some reason. I expect it is related to the problems with Active Directory integration of Lion machines, as described here (among many other places): http://4sysops.com/archives/troubleshooting-the-network-accounts-are-una...

Other than this, I don't know of any big problems with Lion. This is only big if you are trying to integrate Lion machines into an Active Directory based network.

T

bojev's picture

Thanks Thomas and Craig, I think I may wait a while longer since I do not have any burning reason to update at this point.

Frode Bo Helland's picture

I can’t find my Alias.dat file. That’s my issue.

Theunis de Jong's picture

Frode, when writing Lion Apple decided some folders are way too sensitive to have us dumb users mess around, and so "they" in their wisdom, goodwill, and more of that patronizing crap, decided to hide them. If you are fairly sure your file should be around somewhere on your disk, take a look at http://gothick.org.uk/2011/07/19/revealing-lions-hidden-library-folder/

I'm used to browse around with the Terminal and it seems that's unaffected (pending a definite judgment), but I must admit I draw the line at aliasing 'ls' to show *all* of the hidden dot.name "system" items. It's pretty discouraging to see how much overhead there actually is for each folder ...

Frode Bo Helland's picture

I've found the hidden library and showed hidden files, but still no alias.dat ...

dezcom's picture

Frode,
There are several utilities available that allow you to make all hidden files visible--even just temporarily.

hrant's picture

Theunis, right on.

hhp

Frode Bo Helland's picture

Dez. Did you see my last post? I can see hidden files, but alias.dat is nowhere to be found.

dezcom's picture

Frode,
While I succeeded in finding mine, after checking, I notice that it is an older version that I had downloaded a few years ago. Hmmmm, WTF? I wonder if it has been replaced by another kind of file in the current FLS version?
Adam will have to chime in on this to set the record straight.

agisaak's picture

Frode,

I'm not on Lion so I may be off base here, but are you looking in /Library or ~/Library?

My alias.dat file is in /Library/Application Support/FontLab/Data/

It will not be present in ~/Library/Application Support/FontLab/Data/ unless you've actually made a copy of it there.

André

Frode Bo Helland's picture

I’m looking in ~/Library. Is that not the same? If so, how can I access the other library? Edit: found the library folder under my user, but there’s no alias.dat there either.

Frode Bo Helland's picture

I’ve changed my preferences/folders+paths now, so all the files are supposed to be in the documents folder. No change on the alias issue though.

Frode Bo Helland's picture

Waddayaknow! There’s one library for all users (/Library) and one for the active user (~/Library). Am I right? For future reference: you can access these by pressing shift+cmd+g on the desktop or in Finder and typing the path. I found alias.dat in the first one. Thanks, André!

agisaak's picture

Yes, /Library is for all users and ~/Library is just for the current user. Stuff in ~/Library will override stuff in /Library if the same file is present in both.

André

Goran Soderstrom's picture

FontLab 5.1 (latest build) is very stable on Lion for me, and all macros work after some struggle with getting Robofab up and running. But there is very good instructions available now for that.

In fact, FontLab 5.1 has never crashed a single time with Lion, which feels very good. It’s also running so much faster.

Michael Jarboe's picture

Thanks for the info Goran, I've been holding off after hearing about problems with the macros, etc. and haven't wanted to interrupt my workflow. Hopefully it's as simple as updating to Lion, installing FL 5.1, installing Robofab based on the FL Beta forum instructions, then back to business.

Jens Kutilek's picture

But you can have FontLab 5.1 with 10.6.8 too! No need to upgrade to Lion.

BTW, there's now Mountain Lion coming up. Let's hope it won't break FontLab again ;)

Mark Simonson's picture

Well, at least it can't break it in the same way (lack of Intel code pre-5.1).

Michael Jarboe's picture

What do you guys have against Lion?

dezcom's picture

Since FLS5.1 has been revised and since the Robofab installation has been fixed, I have no problem with Lion. I agree with Goran, things are copacetic with Lion and FLS now.

It looks like most of what Apple is doing with Mountain Lion is related to the iPad user conventions. The fundamental changes that Apple made by dropping the older Mac pre-intel code workarounds is now done. Mountain will seemingly be just a way to make all the iToys speak the same dialect.

Mark Simonson's picture

I just finally made the move today. So far, so good. I haven't done extensive testing with my font apps, but at this point I'm not expecting major issues.

Mark Simonson's picture

By the way, Ben Kiel has posted an easy-to-follow video showing how to install RoboFab in Lion for FontLab 5.1:

http://vimeo.com/36877594

Pretty simple, really.

Jens Kutilek's picture

What do you guys have against Lion?

I have nothing against it. I guess it's a decision if you want to make a big step and get a system with many new parts to work (FontLab 5.1 with Lion) or go one change (First FontLab 5.1, new Mac OS later) at a time.

I'm happy with the new, fast FontLab Studio on Snow Leopard, which uses the recent Python version 2.6, and I'm not sure if I'll ever update my Snow Leopard to Lion, because I know for sure that some of my other applications still need to run PowerPC code, the most important one being Creative Suite 3. I've read that I won't be able to print from it without PowerPC support, and I certainly won't pay 1500$ for an upgrade just to be able to continue printing.

(The other stuff I'd hate to see fall behind would be my C64 emulator and DOOM Legacy ;)

.00's picture

What was I thinking getting involved here again.

Back to drawing.

Mark Simonson's picture

I just notice today that TextEdit won't allow access to user-installed fonts in Lion. This is really too bad. TextEdit had better support for OpenType features than any other app from Apple. I don't understand why they would do this. To get people to buy Pages?

Pages, FWIW, has terrible OT support. Presumably, OT support is a system-level thing. If that's so, it seems strange that OT support is so inconsistent among Apple's apps. Maybe they're following Adobe's lead.

dezcom's picture

Mark,
Are you in RTF mode? Textedit defaults to ascii but if you select RTF, you get many more formatting choices.

Michel Boyer's picture

I just checked on my Mac with 10.7.3 and indeed, fonts in ~/Library/Fonts (in the User font folder) are not accessible from TextEdit.

Mark Simonson's picture

RTF: Check. WTF: Check.

Michel Boyer's picture

Presumably, OT support is a system-level thing. If that's so, it seems strange that OT support is so inconsistent among Apple's apps.

What is even more strange is that if I run TextEdit 1.6 on Lion (TextEdit taken from OS X 10.6), User fonts are then accessible from it (with the opentype support).

dezcom's picture

Wonder why 2 of my fonts show up while others don't? They are my most recent so it may have to do with FDK 2.5 recognition?

Mark Simonson's picture

What would the FDK have to do with installed fonts not working in a particular, standard app?

dezcom's picture

That I don't know. I was just trying to figure out what changed since Lion so it was a WAG.

I hate the new Textedit for other reasons. I want the old "save as" command back.

Mark Simonson's picture

Looks like this is a TextEdit problem, not Lion. I am certain it's not a problem with the fonts.

Michel Boyer's picture

Chris,

it is those fonts that are listed when you click on User in FontBook that are not visible from TextEdit 1.7 on OS X 10.7


Those installed on Computer are accessible (and of course you can choose to install your fonts there). Are you sure you can access from TextEdit fonts that are not listed when you click on Computer in FontBook on OS X 10.7?

And I also think the problem is with TextEdit.

dezcom's picture

Michael,
I install my fonts on the computer instead of user,since I am the only user ;-)
Can you run the old version of Textedit on Lion? I sure would like to try that!

Michel Boyer's picture

Can you run the old version of Textedit on Lion?

Yes, I did just that. I clicked on TextEdit 1.6 in a folder mounted with "Connect to Server" from my Mac with Lion and everything seemed to work fine; I ran no extensive test.

Michel

fontdesigner2's picture

As with snow leopard, you'll have issues with Type 1 fonts, but everyone already knows that.

Cristobal Henestrosa's picture

FWIW, I just bought a new iMac with Lion 10.7.3 and TextEdit 1.7 preinstalled, and migrated all my info into the new machine via Time Machine. So far, TextEdit is showing the fonts of both the computer and the user folder.

fontdesigner2's picture

I always hold off on using software that's brand new. I use Snow Leopard and don't see any reason to upgrade yet.

Syndicate content Syndicate content