SVN Helper Script for RoboFab
18th Mar 2007
Following on from my article about version control for typeface development, I’ve updated the “Export to UFO and commit to SVN” python script I used as an example. This present article will be the script’s permanent home.
I can’t offer much in the way of support, and the script does do some heavy lifting (like removing all GLIFs in the UFO before exporting a new one), so please have a good look at the script before using it. I don’t want to be held accountable if your machine starts vomiting kittens. The script is meant to serve as an example use of pysvn in the context of typeface development. Having said that, I find it very useful.
Features
The current version (v1.3) of ExportToUFOCommitSVN.py does the following:
- exports the current font in FontLab to UFO,
- add new GLIFs to the working copy,
- delete removed GLIFs from the working copy (new in v1.1!),
- commit a new revision to the SVN repository.
Requirements
In addition to having a copy of FontLab, you’ll need:
- RoboFab: Python library for font development
- pysvn: SVN extension for python (make sure you get the same version as your own SVN installation if you intend to use both)
Download
ExportToUFOCommitSVN.py v1.3 (2007-03-28)
The script is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike license.
Comments
1.
Brook Elgie - 27th Mar 2007, 4.07 PM
In my rush to get this released, I introduced a bug that stopped it committing. There’s a new version (v1.2) that fixes the problem and simplifies the commit fractionally. Sorry about that.
2.
Brook Elgie - 28th Mar 2007, 3.31 PM
Another day, another bug fix. In the previous fix I didn’t test it properly and it was causing a warning when committing. Again, sorry, this version (v1.3) should be good to go. Colour me embarrassed.
3.
Antonio Cavedoni - 21st May 2007, 1.01 PM
Hey Brook: I’m a designer/developer from Italy and I’m very interested in what you’re doing here. I was wondering if you could setup a public repository with the ExportToUFOCommitSVN code so that other people could work on it with you, maybe on Google Code or on some other venues (I have a shared repository with another friend at unicoders.org as well).
4.
Brook Elgie - 22nd May 2007, 10.24 AM
Hi Antonio, perhaps we could get something setup. I’ve sent you a rather long-winded email.
5.
Dave Crossland - 5th Oct 2007, 3.45 PM
Hi Brook!
With Tal releasing some code under the MIT license, I thought I’d drop you a line about releasing this under a functional-work/software license rather than a artistic-work license.
Best,
Dave
6.
Brook Elgie - 8th Oct 2007, 8.39 AM
Hi Dave - I definitely agree CC isn’t the best license for this stuff. Just happened to be the only one I was familiar with. I’ll look into some alternatives.
7.
Joancarles Casasín - 18th Oct 2007, 10.01 AM
Is this working (or is there a way to make it work) in Intel Macs? it gives me a traceback with :
(…)
/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/pysvn/_pysvn.so: mach-o, but wrong architecture. Thanks.
8.
Brook Elgie - 18th Oct 2007, 10.46 AM
@Joancarles - Because Fontlab runs in Rosetta as a PowerPC application, you need to install the PPC version of the package for python 2.3 (from the list here).
Comment preview: