For the five minutes I've been playing with it, it seems to work, but only time will tell... I've a VM on standby with Mavericks just-in-case.

AFDFO seems to work fine from the command line.
I don't have the FL macros on my MacBook... can try a bit later on the iMac where I think I have them... and if worst comes to the worst I think I have an old copy of AFDKO lurking around where they were present.

I guess it is about time for me to learn how to use AFDKO from Terminal... I am so dense that I haven't ever really been able to figure out how to run autohint and checkoutlines, the only 2 things I really need from the AFDKO. I read over the help files as well, and it somehow didn't really help me, haha.

Looks like this is my homework for the day...

EDIT: nevermind! figured it out.

David, if you could humor me for a second, can you explain how to specify the location of the OTF file I want to use in AFDKO in terminal?

for example, if I want to run checkOutlines on a file, how do I tell it where the file is located?

You can either append the full pathname to the file after checkoutlines... or cd to the directory then just append the filename.
e.g. on OS X:
checkoutlines ~/Documents/Foundry/fred/fred.otf
or
cd ~/Documents/Foundry/fred/
checkoutlines fred.otf

FontLab knows of no issues with FontLab Studio 5.1.4 in Yosemite. Seems to be just fine. Ditto latest versions of Fontographer and TypeTool.

You can either append the full pathname to the file after checkoutlines... or cd to the directory then just append the filename.

Just drag the file from the Finder to the active window of Terminal, that’s even easier…

I should add two caveats:

- Folks using some Wacom tablets may find that they need old drivers for the tablets to work properly with FontLab Studio (and with assorted other apps), but that the old drivers are not compatible with Yosemite.

- We have one report that while they still work, UFO export scripts (both from Robofab and UFO Central) seem to be surprisingly slow under Yosemite. I'd be curious to hear if more people have experienced this slowdown.

I've noticed a problem.

Randomly I lose certain keyboard or cursor key functions. I was just editing a glyph and selected the tool to draw a circle from the toolbar. When I pressed 1 to return to the pointer tool nothing happened. I also lost the z and x zoom ability. Also lost was the delete key function and the command x for cut. These functions continued to work when selected via menu. When I pressed the ` key for high rez preview the preview remained after I released the key. Cursor keys continued to function.

On other occasions I have lost cursor key function. It is all appears to be random. I will pay closer attention to see if I can identify a pattern.

I've found in general things work as well under Yosemite as they did under Mountain Lion. However, today I did have Fontlab crash on me a few times in a row. A glitchy font file might be to blame here, I'll have to see if it happens again with a different font. In using my Wacom tablet, I find the screen scrolls up by a couple of inches whenever I put pen to tablet, but it's done that since Snow Leopard, so I'm not too concerned (though I'd love to have a fix for this).

Cheers,

Oliver

Prior to Yosemite, the fix for the tablet problem was to downgrade to an older driver for the tablet. However, that older driver no longer works under Yosemite.

I was rather unimpressed with the fuzzy and pixelated UI. There seems to be no support for Retina displays.

Hi, I run Fontlab studio 5.1.3 on both my Mac Pro and Macbook Pro. On both Yosemite is the OS. On my MacPro (almost) everything is working, but on my MacbookPro the “assign to keyboard” button is not working, clicking on button or triangle next to it is doing nothing. So, it works on MacPro but not on MacBookPro, any idea? Thanks!