MacOS X 10.9 Mavericks: Any issues?

I've not made the upgrade, but since the new Mac OS version 10.9 is a free upgrade to users with access to Apple's App Store (basically 10.6 Snow Leopard and newer, as far as I can tell) I expect to make the plunge once I nail down some backup issues.

Have any of you made the upgrade? How are the type handling features compared to earlier versions? How is the FontBook? Are your font design or other graphics software experiencing new problems since the system upgrade?

Comments

  • The only font app I'm sure is 10.9 compatible is Glyphs. I haven't upgraded yet and intend to wait because others, such as FontLab and Adobe (CS6), haven't said anything yet.
  • i just upgraded to 10.9 this morning. robofont runs just fine as does the afdko. most everything works the same as in mountain lion. post install, i think i got a few free gigs of disk space. that was nice. i had an old version of vmware fusion that osx notified me would be inoperable during the upgrade.

    i upgraded a late 2008 macbook running snow leopard and an early 2011 macbook pro. only real 'issue' you'll notice is spotlight will want to index your machine for the next few hours after the install finishes. if you're not rocking an ssd, your laptop will be mostly unusable while this happens.

    only real snag: i was having some issues getting cs4 applications to work so i uninstalled them in the interim. i read this adobe mavericks faq and it implied that the apps should work, maybe i just need to reinstall them? an adobe cc trial works just fine on mavericks, fwiw, at least until i decide if i'll try to reinstall or just upgrade outright. i get the impression cs6 works just fine, but not surprised at all that cs4 gave up the ghost. this is not a very big source of concern for me in any case.
  • Perhaps check out
    http://roaringapps.com
    for compatibility issues?
  • [Deleted User][Deleted User] Posts: 0
    edited October 2013
    The user and all related content has been deleted.
  • I upgraded last week and have not had any problems with FontLab, Robofont, Glyphs, etc. There is an update needed for Superpolator, however. Lastly, if you have Python things (e.g., Fonttools) installed, see this tweet by Ben Kiel: . (The upgrade wipes out any site-packages folders you've installed, so you have to restore them.)
  • i did not notice my /Library/Python/2.7/site-packages being cleaned out after running an upgrade.
    image
    i wouldn't have thought to check... did this happen to other folks? did a different site-packages folder get cleaned out?
  • The user and all related content has been deleted.
  • i thought i would follow up and clarify about the cs4 issue i had

    it turns out that cs4 expects java to be installed (i believe in order to run the the little Did You Know widget in the New Document panel that opens) but i dismissed the java installer when i first saw it since i couldn't remember the last time i'd used java anyway.

    anyhow, after installing that java runtime, cs4 works just as before under mavericks in case that was a source of concern for you.

    --cs4eva
  • Sorry I'm late to the party.
    No problems with FontLab or RoboFont.
    Thank you to Ben for the tip about the site-packages (bonus Thank You to Time Machine).


    I'm noticing some weird issues with Type 1 fonts.
    Installing a font via FontBook will only import the suitcase, not the printer file.
    The font does display in FontBook if you copy the printer file to the Fonts folder.
    Once installed, the fonts aren't available in InDesign (5.5 or 6) or Word. They do show up in TextEdit.
    Is anyone else experiencing this?
  • I am not seeing this problem. I don't use Font Book, though. I manage fonts by manually moving fonts in an out of ~/Library/Fonts/. Perhaps there was a cache issue from when only the suitcase file was installed?
  • Update: FontBook cannot install Type 1 fonts

    I ran FontNuke and Type 1 fonts display in Adobe apps & Word.
    Font Book only installs the suitcase file, but not the printer file.
    The font still does not work if you copy the printer file to the Fonts folder.
    However, manually installing a Type 1 font works just fine.
  • I echo Marcos in that all my Python site-packages went poof! In fact, I've been unable to re-install them properly since no matter what installer method I use, it's only installing in the frameworks subdirectory.

    Thinking it's time to start a Python one-click magic button installer Kickstarter for Glyphs and FLAB and be done with all this Python install BS which seems to be a constant time suck . . .
  • Thank you Paul, already performed it as well as MekkaBlue's line by line terminal instructions. Neither has found its remedy . . .

    If indeed one or both of these should work 99% of the time, I'm willing to assume user error but given the time already invested, I'm at a point where I'd happily commission a tool to simply fix my Python/Glyphs/Robofab install issues once and for all.
  • Thinking it's time to start a Python one-click magic button installer Kickstarter for Glyphs and FLAB and be done with all this Python install BS which seems to be a constant time suck . . .
    how much would you pay for it ;)
  • Chris LozosChris Lozos Posts: 1,458
    "how much would you pay for it ;)"
    If you build it, they will come.
  • I'd pay $50 to never have to deal with it and I'd pay an additional $50 toward its development for the good of the community.
  • [Deleted User][Deleted User] Posts: 0
    edited November 2013
    The user and all related content has been deleted.
  • I want this to work more than you can know . . . I'm getting the same error on both my 10.6.8 and 10.9 machines . . . See attached image:
  • Can you re-download the script? I think I fixed it.
  • That fixed it!
  • I believe everything installed properly however when I run the very basic single test from Ben Kiel's video, I get a pile of errors which doesn't explain what may be happening or why. Thoughts?
  • Fixed it again. Now it should work properly.
  • Sorry, new error . . . The installer won't run now . . .
  • The user and all related content has been deleted.
  • Dunno if Georg wants to officially announce it but it is now fully working for me!
  • Georg, instead of using sudo everywhere, since this script is already osx specific, you could run this
    sudo chmod +a "user:$USER allow add_subdirectory,add_file,delete_child,directory_inherit" /Library/Python/2.7/site-packages
    which makes all of the user site-packages user-writable so you don't always have use sudo all the time when pip installing things globally and you don't need to sudo in order to throw stuff away. you can learn more on hombrew's wiki. as far as i know, osx doesn't mess with this folder during system upgrades.

    you could put the whole thing up in a gist so that it can be easily forked but without the overhead of a whole repo. thanks!
  • as far as i know, osx doesn't mess with this folder during system upgrades.
    As far as I know OSX is replacing this folder on every major update.

    Will put this in git soon. Just wanted it to be working first.

    Thanks for the sudo info. Will try it.
Sign In or Register to comment.