optionally specify locations of afdko, ttfautohint in prefs

RoboFont Forums Features optionally specify locations of afdko, ttfautohint in prefs

This topic contains 1 reply, has 2 voices, and was last updated by  frederik 3 years, 10 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #5727

    Marcos Ojeda
    Member

    right now these values are hardcoded within the app. for example, the test for the afdko seems to be whether or not the binaries show up in the adobe-recommended ~/bin/FDK/Tools/osx

    ttfautohint is a bit more mysterious (i can’t figure out how to get it to enable the ttf autohint checkbox to work even though mojo.compile.hasTTFAutoHint returns true for my version of ttfautohint installed via homebrew).

    regardless, it would be easier to debug this behavior if these search paths were easy to set. i think the current behavior probably satisfies many common-cases, but i suspect that there is wide variability in the location of sundry binaries.

    thanks!

    #5730

    frederik
    Keymaster

    It is indeed recommended for FDK to be installed on a specific path.

    For ttfautohint RoboFont is checking it with which ttfautohint terminal command to see if it installed on your local machine. In a normal setup it should be something like /usr/local/bin/ttfautohint
    Next to be installed ttfautohint requires an ‘o’ glyph in the font otherwise it just fails to autohint. (see ttfautohint -h)

    hope this helps.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.