1. Fontlab Studio 5.1.2 Pre-release Build 4447 For Mac

I've just tested those instructions to install RoboFab with FontLab Studio 5.1 build 4311 and Mac OS X 10.7.2. They work fine. Since the system Python 2.7 in Mac OS X 10.7.2 comes with pre- installed NumPy, it's no longer necessary to install NumPy. Therefore, if you're on Mac OS X 10.7.2 and you have FontLab Studio 5.1 build 4311 or newer installed, do the following: 1. Quit FontLab Studio. In Finder, navigate to the location where you downloaded the.zip file, double-click to unzip it (if it already hadn't happened). You should see a folder named 'RoboFab226MplusDependencies'.

Open the Terminal app 4. In Terminal, type 'cd ' (with a trailing space) but don't hit Enter. Drag the RoboFab226MplusDependencies folder to the Terminal window. You should see something like this in the Terminal window: cd /users/your username/Downloads/RoboFab226MplusDependencies 5.

In Terminal, hit Enter. In Terminal, do the following: (Hit Enter after each line. After the first 'sudo' you'll need to enter your administrator password.) cd FontTools sudo /usr/bin/python setup.py install cd. Cd RoboFab sudo /usr/bin/python setup.py install cd. Cd DialogKit sudo mv Lib/dialogKit/ /Library/Python/2.7/site-packages/ 7.

In Finder, do File / New Finder Window 8. If you have enabled 'Use custom locations for user data folders' in FontLab Studio / Preferences / General Options / Folders and paths, navigate Finder to folder that you've set as the 'FontLab Studio user data files' folder, and skip to step 8. If you have not customized the location, then in Finder's menu, choose Go / Go to Folder. In the text box that appears, enter: /Library/Application Support/FontLab/Studio 5/Macros and click on Go. Your Finder should now should show a Macro folder with at least three subfolders in it (Effects, Export and System).

Switch to the Finder window that has the RoboFab226MplusDependencies folder, and open the subfolder RoboFab/ Scripts folder that is inside. You should see a folder with several subfolders: 'Contributed', 'RoboFabIntro', 'RoboFabUFO', 'RoboFabUFO2', 'RoboFabUtils'. Select those folders and drag them to the Macro folder in the other Finder window. Open FontLab Studio and in the Edit Macro panel type in: import robofab import dialogKit If you don't see anything in the Output panel, you have installed RoboFab and its FontLab macros and DialogKit successfully. Best, Adam Adam Twardoch, 8:47 น.

Adam, These look good. I'd just note that any scripts using dialogs from RoboFab likely won't work with the robofab download you linked to. The svn version is a better choice currently. To edit your instructions, I'd say this: 2. Create a folder for your RoboFab and other sources. It doesn't really matter where this folder is, or what it is called, but a good practice would be to put in in your user folder, name it with just one word —no spaces or glyphs outside of ascii. For example, my folder for such things is /benkiel/code/.

The easiest way to make said folder is to open up Terminal.app, and type: mkdir /code Replace 'code' with whatever you want to call your source folder. Hit enter 3. Open Terminal.app if you haven't already 4. In terminal, type: cd /code (of course, if you've called the folder something else, use that) Hit enter 5. Next, you'll need to checkout the svn robofab, dialogkit and fonttools. You must be online for the following to work.

This is simply done by typing: svn checkout Hit enter, watch things scroll. Next, you'll need to get dialog kit. This can also be done with a svn checkout. Type: svn checkout Hit enter, watch things scroll. Lastly, you'll need FontTools.

Again, a svn checkout will get you that. Type: svn checkout Hit enter, watch things scroll. If you now type ls in terminal you should see the following three folders: benBookPro-2:test benkiel$ ls dialogKit fonttools 6. In Terminal, do the following: (Hit Enter after each line.

After the first 'sudo' you'll need to enter your administrator password.) cd fonttools/trunk sudo /usr/bin/python setup.py install cd./. Cd sudo /usr/bin/python install.py cd./. Cd dialogKit/trunk sudo /usr/bin/python install.py Best, Ben - You received this message because you are subscribed to the Google Groups 'RoboFab' group. To post to this group, send email to To unsubscribe from this group, send email to For more options, visit this group at Messages from newly joined members are subject to moderation. Download RoboFab and documentation at !DSPAM:4eaaca311248! Ben Kiel Direct Dial: (302) 766-7593 Erik van Blokland, 14:59 น. James, Sounds similar to what I was experiencing before.

Which RoboFab download did you use? On 11-10-28 23:59, Erik van Blokland wrote: The one to get would be RoboFab rev.483 + (up to date) dependencies: Also, you may need to redefine the path back as per Adam's '8. If you have enabled 'Use custom locations for user data folders' in FontLab Studio / Preferences / General Options / Folders and paths, navigate Finder to folder that you've set as the 'FontLab Studio user data files' folder.' ChrisL On Nov 9, 1:04 pm, James Puckett wrote: I am trying to get Fontlab 5.1 and Robofab working on a new mac running 10.7. I tried Adam’s instructions using the latest package at Robofab.org. I can import robofab and dialog kit.

On 11-11-11 23:39, James Puckett wrote: Thanks Ben, that worked. I stripped all references of ProgressBar from UFOCentral and it seems to work fine, albeit so quickly that it seems to do nothing;).

I attached my “working” version if anybody else needs it. That's interesting.

I recently did a similar thing: I realized that in some operations, the progress bar, especially a very finely grained one, is the reason for actually slowing down the operation in a notable way. I got rid of some of those myself in various macros I've written:) David Cabianca 1/1/2012, 15:59 น.

I am sorry to add to the list. I have read through the threads and I see a lot of effort on the part of Erik, Tal, Ben, Adam and others to sort this problem out. I am sorry to add to the pile.

I have tried the recommendations above by Adam and Ben. I have reinstalled FontLab 5.1 and 5.1.1. I have reinstalled RoboFab quite a few times. Unfortunately all I can get out for my Fontlab now is a similar message as below, no matter what script I try, they all end with 'ImportError: No module named misc.arrayTools.' I am using OSX 10.7.2, and with Python 2.7.2 (v2.7.2:a2, Jun 11 2011, 15:22:34); My FontLab is using 2.7.1 (r271:86832, Jun 16 2011, 16:59:06). If anyone has any suggestions, please let me know.

Sorry to be such a newbie. Traceback (most recent call last): File ', line 29, in File '/Library/Python/2.7/site-packages/robofab/world.py', line 95, in from robofab.objects.objectsFL import CurrentFont, CurrentGlyph, RFont, RGlyph, OpenFont, NewFont, AllFonts File '/Library/Python/2.7/site-packages/robofab/objects/ objectsFL.py', line 6, in from robofab.objects.objectsBase import BaseFont, BaseGlyph, BaseContour, BaseSegment, File '/Library/Python/2.7/site-packages/robofab/objects/ Erik van Blokland 4/1/2012, 3:06 น. Hi David, the problem is that the 2.7.2 is 'occupying' the command line. So when you type 'python', you end up working with 2.7.2, rather than the 2.7.1.

So all your install efforts go towards 2.7.2. It's a nuisance the folks at Python and the folks at Apple decided to deal with Python sub versions (2.7.1 vs 2.7.2) in such a way.

From our earlier correspondence I know: python version 2.7.1 (r271:86832, Jun 16 2011, 16:59:06) site-packages is at /Library/Python/2.7/site-packages python version 2.7.2 (v2.7.2:a2, Jun 11 2011, 15:22:34) site-packages is at /Library/Frameworks/Python.framework/Versions/2.7/ lib/python2.7/site-packages If you open the 2.7.2 site-pacakges folder you will see the results of your install work. Robofab, DialogKit, Vanilla, FontTools - either pointed to by.pth files or as actual packages in folders. Now open the 2.7.1 site-packages folder in another window. It is probably rather empty.

The easiest thing to try would be to proceed to.copy. all files and folders that relate to RoboFab, DialogKit, FontTools, Vanilla (including files ending in.pth and folders) from one to the other. This might require you to type your password. That will put all the modules on the search path for the 2.7.1 python, and they will be available to FontLab 5.1.

Erik Erik van Blokland 4/1/2012, 4:27 น. FontLab Studio 5.1 links to the Python framework present in: /System/Library/Frameworks/Python.framework/Versions/Current This is always the Python framework pre-installed by Apple. (Note: It wasn't completely easy to do for our developers, since 'Current' is an alias and XCode requires a real path. So the application does a bit of trickery itself to work around that limitation.) However, we're not at this time able to link to 'any' Python available on the system.

In other words, if you've installed a custom Python from or fink or MacPorts or homebrew or using any other method, FontLab Studio won't be able to access it - simply because there are just too many ways in which Python can be built and installed. So while FontLab Studio 5.1 is more flexible than the previous versions, because it links to the most current version of Python.pre-installed by Apple. on Mac OS X, it won't link to.just any. Python. Especially not to the Python that the user installed him/herself.

We will investigate the possibility of making the version of Python used by FontLab Studio selectable by the user from within the application. But I can't promise that it'll be done, because at this moment I don't know if it can easily be done. Best, Adam - May success attend your efforts, - Adam Erik van Blokland 4/1/2012, 10:21 น.

A structural and useful approach would be to have a pref in FontLab where I can add paths to addional modules that will be added to FontLab's sys.path. The setup would then become part of FontLab's responsibility, save nicely with its other prefs and so on. It would be a nice non-robofab specific solution to the FontLab python setup. Adding stuff to sys.path is really simple. Adding a window and a pref wouldn't break the bank either (well, if I write them in python they wouldn't— not sure how that goes in C) But — Can you give us that? On Jan 4, 12:27 pm, Erik van Blokland wrote: Another thing you could try is to find out the actual path the 2.7.1 python What do you get when you do this in Terminal: cd /usr/bin ls -la py. Here is the output. David: Out of curiosity, what's in your /hard drive/Library/Python/2.7/site-packages folder?

Quick way to dump that out is go to terminal and type: cd /Library/Python/2.7/site-packages ls -a Best, Ben - You received this message because you are subscribed to the Google Groups 'RoboFab' group. To post to this group, send email to To unsubscribe from this group, send email to For more options, visit this group at Messages from newly joined members are subject to moderation. Download RoboFab and documentation at !DSPAM:4f0ae7694347!

Ben Kiel Direct Dial: (302) 766-7593 David Cabianca 10/1/2012, 12:14 น.

There are a host of utilities that can make the font making and editing experience easier and faster. Some work directly in FontLab Studio via the Python scripting language, and others are separate items. Here is how to install Python-related tools, and the many scripts and things they enable, to work with FontLab Studio 5.1+ on Mac OS and Windows. (If you are using earlier versions, please upgrade to 5.1.x Mac and 5.2.x Windows. Upgrades from 5.0 and higher are free!) You do not have to be a programmer to make use of these tools! While folks who are at least moderately geeky and technical will get more out of most of these tools, almost anybody who can use FontLab Studio will find value in tools such as TTX, and benefit from some scripts they can run “out of the box.” Once you get this stuff set up, you can install more macros/scripts just by dragging them to the FontLab macros folder, and restarting FontLab Studio.

Note: Hard core techno-geeks may want to just skip ahead to the “step by step” instructions for their OS of choice. Thanks to Just van Rossum, Tal Leming, Erik van Blokland, Behdad Esfahbod, Guido van Rossum, and the entire awesome community of people who have contributed to these many pieces. Also thanks to Adam Twardoch for his October 2011 writeup on installation, from which I have stolen borrowed extensively. Overview & Background Installing some of these pieces will require “administrator” privileges on your computer.

As long as you have this capability, the instructions below will cover how to doit. If you do not have admin privileges, you will have to get somebody who does to do it for you, or forego these tools and add-ons.

NOTE: Download links for exactly what you need to install will come later; links in this section are just for general info. It is a programming and scripting language, invented by Guido van Rossum, which is increasingly popular for many tasks. But even if you do not want to write scripts yourself, it can be handy to use Python scripts in FontLab Studio, and the TTX program that installs with the Python FontTools library is of use to anybody who wants to investigate or hack fonts. The other bits described below are used by some third-party Python scripts for FontLab Studio, and while not strictly required can be useful if you want to write scripts yourself. The next most useful related piece is, a Python library that provides objects that deal with font-related data.

May FontLab scripts and tools are dependent on RoboFab. are a pair of related things. TTX is a tool to convert OpenType and TrueType fonts to and from XML. FontTools is a library for manipulating fonts, written in Python. TTX requires FontTools, and the two install together.

These utilities were created a long time ago by Just van Rossum (brother of Guido), and their existence is the reason Python became the de facto standard reason for font processing and programming. A of TTX/Fonttools is maintained by Behdad Esfahbod. is a Mac-only Python library developed by Tal Leming which makes it easy to build native Mac dialogs and interfaces with Python, which can work with FontLab Studio or other Mac OS X Cocoa applications that have a Python layer. It gives control over many kinds of GUI widgets such as windows, buttons, input fields, sliders etc. However, scripts designed to use Vanilla (without graceful fallback) will be Mac-only.

Fontlab Studio 5.1.2 Pre-release Build 4447 For Mac

is a Python-only subset of Vanilla, which can work with FontLab Studio or other applications that have a Python layer. Step by Step Mac Install For a Mac user, we suggest installing Robofab, TTX/Fonttools, DialogKit and Vanilla. Mac users will already have Python installed.

If you haveMac OS 10.7–10.9, you already have Python 2.7 (and NumPy), which you need to go along with FontLab Studio 5.1.x. Although there are all-in-one installers for the bits below, they are getting a bit old; we instead recommend Requirements:. FontLab Studio 5.1.x (we have tested with 5.1, 5.1.2 and 5.1.4; FontLab Studio 5.0.x requires an earlier Python; we recommend upgrading to the most recent version of FontLab Studio.). Mac OS X 10.7, 10.8, or 10.9.

Since the system Python 2.7 in Mac OS X 10.7 and later comes with pre-installed NumPy, it's no longer necessary to install NumPy. Instructions:.

Quit FontLab Studio if it is open. Download these files:.

Note on license terms: All of the above software is licensed to you under “non-viral” open source licenses. FontTools has a. Robofab is under the. In Finder, navigate to the location where you downloaded your files. Find each zip file and double-click to unzip it (if it hasn’t already happened). The four zip files and their resulting folders are:.

fonttools-master.zip file folder named “fonttools-master”. RoboFab599only.zip folder named “RoboFab”. vanilla-master.zip  folder named “vanilla-master”. dialogKit-master.zip file folder named “dialogKit-master” So now you have the four unzipped folders, right?. Open the Terminal app. In Terminal, type “cd ” (with a trailing space) but don’t hit Enter. Drag the “fonttools-master” folder to the Terminal window.

You should see something like this in the Terminal window: cd /users/your username/Downloads/fonttools-master. In Terminal, hit the Enter/Return key. In Terminal, do the following: (Hit Enter after each line. FEA Error Message Issue Warning Message when generating an Opentype font in Fontographer. “ feature block seen before any language system statement. You should place language system statements before any feature definition” Solution 1.

An FEA file is a feature file which is created to add Opentype features to a font. Most users who contact tech support ask us why they are getting this message.

It follows that they were NOT intending to edit an FEA file. If you were not intending to edit an FEA file then you can safely ignore this message. If you have no intention of editing an FEA file you can prevent this warning from appearing by electing Element Font InfoEncoding and turning ON the radio button which says, “Do not generate Opentype Layout Code.” 3. If you DO want to edit an FEA file then you may need to compare yours to a working FEA file to determine why you are getting the warning.

Here is a link for a working FEA sample file.