Scripting FontForge

FontForge includes two interpreters so you can write scripts to modify fonts. One of these interpreters is python, one is a legacy language I came up with. FontForge may be configured with either or both of these. If configured with both then fontforge will make a guess at which to use based on the script file’s extension (“py” means use the python interpreter, “ff” or “pe” means use the old interpreter)

Invoking scripts

If you start fontforge with a script on the command line it will not put up any windows and it will exit when the script is done. The script can be in a file, or just a string presented as an argument. You may need to specify which interpreter to use with the -lang argument.

$ fontforge -script {arguments}
$ fontforge -c "script-string" {arguments}
$ fontforge -lang={ff|py} -c "script-string"

FontForge can also be used as an interpreter to which the shell will automatically pass scripts. If you a mark your script files as executable

$ chmod +x

and begin each one with the line


(or wherever fontforge happens to reside on your system) then you can invoke the script just by typing

$ {fontnames}

If you wish FontForge to read a script from stdin then you can use “-” as a “filename” for stdin. (If you build FontForge without X11 then fontforge will attempt to read a script file from stdin if none is given on the command line.)

You can also start a script from within FontForge with File ‣ Execute Script, and you can use the Preference Dlg to define a set of frequently used scripts which can be invoked directly by menu.

The scripting language provides access to much of the functionality found in the font view’s menus. It does not currently (and probably never will) provide access to everything. (If you find a lack let me know, I may put it in for you). It does not provide commands for building up a glyph out of splines, instead it allows you to do high level modifications to glyphs.

If you set the environment variable FONTFORGE_VERBOSE (it doesn’t need a value, just needs to be set) then FontForge will print scripts to stdout as it executes them.

You may set the environment variable FONTFORGE_LANGUAGE to either “py” (for python) or “ff” or “pe” (for native scripting) as another way to determne what interpreter to use.

Scripting Language


This section covers FontForge’s native scripting functionality.

For the Python scripting functionality, see here.

The syntax is rather like a mixture of C and shell commands. Every file corresponds to a procedure. As in a shell script arguments passed to the file are identified as $1, $2, … $n. $0 is the file name itself. $argc gives the number of arguments. $argv[<expr>] provides array access to the arguments.

Terms can be

  • A variable name (like “$1” or “i” or “@fontvar” or “_global”)

    The scope of the variable depends on the initial character of its name.

    • A ‘$’ signifies that it is a built-in variable. The user cannot create any new variables beginning with ‘$’. Some, but not all, of these may be assigned to.

    • A ‘_’ signifies that the variable is global, it is always available. You can use these to store context across different script files (or to access data within nested script files).

    • A ‘@’ signifies that the variable is associated with the font. Any two scripts looking at the same font will have access to the same variables.

    • A variable which begins with a letter is a local variable. It is only meaningful within the current script file. Nested script files may have different variables with the same names.

  • an integer expressed in decimal, hex or octal

  • a unicode code point (which has a prefix of “0u” or “0U” and is followed by a string of hex digits. This is only used by the select command.

  • a real number (in “C” locale format – “.” as the decimal point character)

  • A string which may be enclosed in either double or single quotes. String tokens are limited to 256 bytes. “n” can be used to represent a newline character. (If you need longer strings use the concatenation operator).

  • a procedure to call or file to invoke.

  • an expression within parentheses

  • a series of expressions (separated by commas) within brackets, as [1, 2, 3, 5, 8], used to create an array.

There are three different comments supported:

  • Starting with a “#” character and proceeding to end of line

  • Starting with “//” and proceeding to end of line

  • Starting with “/” and proceeding to “/”


Expressions are similar to those in C, a few operators have been omitted, a few added from shell scripts. Operator precedence has been simplified slightly. So operators (and their precedences) are:

  • unary operators (+, -, !, ~, ++ (prefix and postfix), –(prefix and postfix), () (procedure call), [] (array index), :h, :t, :r, :e

    Most of these are as expected in C, the last four are borrowed from shell scripts and are applied to strings

    • :h gives the head (directory) of a pathspec

    • :t gives the tail (filename) of a pathspec

    • :r gives the pathspec without the extension (if any)

    • :e gives the extension

  • *, /, % (binary multiplicative operators)

  • +, - (binary arithmetic operators)

    If the first operand of + is a string then + will be treated as concatenation rather than addition. If the second operand is a number it will be converted to a string (decimal representation) and then concatenated. If the first operand of + is an array then + will do array concatenation – if the second argument is also an array the two will be concatenated ([1,2] + [3,4] yields [1,2,3,4], while [1,2] + 3 yields [1,2,3]). Otherwise these are the normal arithmetric operations.

  • ==, !=, >, <, >=, <= (comparison operators, may be applied to either two integers or two strings)

  • &&, & (logical and, bitwise and. (logical and will do short circuit evaluation))

  • ||, |, ^ (logical or, bitwise or, bitwise exclusive or (logical or will do short circuit evaluation))

  • =, +=, -=, *=, /=, %= (assignment operators as in C. The += will act as concatenation if the first operand is a string.)

Note there is no comma operator, and no “?:” operator. The precedence of “and” and “or” has been simplified, as has that of the assignment operators.

Procedure calls may be applied either to a name token, or to a string. If the name or string is recognized as one of FontForge’s internal procedures it will be executed, otherwise it will be assumed to be a filename containing another fontforge script file, this file will be invoked (since filenames can contain characters not legal in name tokens it is important to allow general strings to specify filenames). If the procedure name does not contain a directory then it is assumed to be in the same directory as the current script file. As a convenience, it is not necessary to include the script’s extension if it is either “.ff” or “.pe”. At most 25 arguments can be passed to a procedure.

Arrays are passed by reference, strings and integers are passed by value.

Variables may be created by assigning a value to them (only with the “=”), so:


could be used to define “i” as a variable. Variables are limited in scope to the current file, they will not be inherited by called procedures.

A statement may be

  • an expression

  • if ( expression )
    {elseif ( expression )
  • while ( expression )
  • foreach
  • break

  • return [ expression ]

  • shift

As with C, non-zero expressions are defined to be true.

A return statement may be followed by a return value (the expression) or a procedure may return nothing (void).

The shift statement is stolen from shell scripts and shifts all arguments down by one. (argument 0, the name of the script file, remains unchanged.

The foreach statement requires that there be a current font. It executes the statements once for each glyph in the selection. Within the statements only one glyph at a time will be selected. After execution the selection will be restored to what it was initially. (Caveat: Don’t reencode the font within a foreach statement).

Statements are terminated either by a new line (you can break up long lines with backslash newline) or a semicolon.

Trivial example:

i=0;   #semicolon is not needed here, but it's ok
while ( i<3 )
   if ( i==1 /* pointless comment */ )
        Print( "Got to one" )   // Another comment

FontForge maintains the concept of a “current font”– almost all commands refer only to the current font (and require that there be a font). If you start a script with File ‣ Execute Script, the font you were editing will be current, otherwise there will be no initial current font. The Open(), New() and Close() commands all change the current font. FontForge also maintains a list of all fonts that are currently open. This list is in no particular order. The list starts with $firstfont.

Similarly when working with cid keyed fonts, FontForge works in the “current sub font”, and most commands refer to this font. The CIDChangeSubFont() command can alter that.


All builtin variables begin with “$”, you may not create any variables that start with “$” yourself (though you may assign to (some) already existing ones)


the current script filename


the first, second (…) argument to the script file


the number of arguments passed to the script file (this will always be at least 1 as $0 is always present)


allows you to access the array of all the arguments


the name of the filename in which the current font resides


the name of the filename of the font which is first on the font list (Can be used by Open()), if there are no fonts loaded this returns an empty string. This can be used to determine if any font at all is loaded into fontforge.


the name of the filename of the font which follows the current font on the list (or the empty string if the current font is the last one on the list)


returns 1 if the current font has changed, 0 if it has not changed since it was read in (or saved).


the name contained in the postscript FontName field


the name contained in the postscript FamilyName field


the name contained in the postscript FullName field


if set this name indicates what FOND the current font should be put in under Generate Mac Family.


the name contained in the postscript Weight field

the name contained in the postscript Notice field


the name of the file containing the font.


the string containing the font’s version


1 if the current font is a cid keyed font, 0 if not


returns the fontname of the top-level cid-keyed font (or the empty string if there is none)

Can be used to detect if this is a cid keyed font.

$cidfamilyname, $cidfullname, $cidweight, $cidcopyright

similar to cidfontname


returns 0 for non multiple master fonts, returns the number of instances in a multiple master font.


the value of the postscript italic angle field


a bitmask of non-fatal errors encountered when loading the font.


a bitmask of some errors in the PostScript Private dictionary (see fontforge.font.privateState for more info).


returns the fontname of the current font


returns the fontname of the first font within this cid font


returns the fontname of the next font within this cid font (or the empty string if the current sub-font is the last)


returns the value of the macstyle field (a set of bits indicating whether the font is bold, italic, condensed, etc.)


returns an array containing all bitmap pixelsizes generated for this font. (If the font database contains greymaps then they will be indicated in the array as (<BitmapDepth><<16)|<PixelSize>)


returns an integer containing either 2 (for truetype fonts) or 3 (for postscript fonts). This indicates whether the font uses quadratic or cubic splines.


returns the number of em-units used by the font.


returns the ascent of the font


returns the descent of the font.


returns an array containing one entry for each glyph in the current font indicating whether that glyph is selected or not (0=>not, 1=>selected)


returns an array containing the 10 panose values for the font.


if this is set to one then FontForge will trace each procedure call.

returns a string containing the current version of fontforge. This

should look something like “20050817”.


returns 1 if python scripting is available, 0 if it is not.


  • $<Preference Item> (for example $AutoHint) allows you to examine the value of that preference item (to set it use SetPref())

The following example will perform an action on all loaded fonts:

file = $firstfont
while ( file != "" )
   /* Do Stuff */
   file = $nextfont

The built in procedures are very similar to the menu items with the same names. Often the description here is sketchy, look at the menu item for more information.

Built-in procedures in alphabetic order

Built-in procedures that do not require a loaded font

Built-in procedures that act like the File Menu

File Manipulation

Built-in procedures that act like the Edit Menu

Built-in procedures that act like the Select Menu

Built-in procedures that act like the Element Menu

Font Info

Glyph Info

Built-in procedures that handle Advanced Typography

Built-in procedures that act like the Encoding Menu

Built-in procedures that act like the Hint Menu

Built-in procedures that act like the Metrics Menu

Multiple master routines

CID routines

User Interaction




String manipulation

Character Manipulation



Deprecated Names


Example 1:

#Set the color of all selected glyphs to be yellow
#designed to be run within an interactive fontforge session.

Example 2:

#This is the sfddiff script which compares two fonts

if ( Strtol($version) < 20060330 )
  Error( "Please upgrade to a more recent version of fontforge" )


while ( $argc > 1 && Strsub($1,0,1)=="-" )
  temp = $1
  if ( Strsub(temp,1,2)=='-' )
    temp = Strsub(temp,1)

  if ( temp=="-ignorehints" )
    flags = flags & ~0x8
  elseif ( temp=="-ignorenames" )
    flags = flags & ~0x100
  elseif ( temp=="-ignoregpos" )
    flags = flags & ~0x200
  elseif ( temp=="-ignoregsub" )
    flags = flags & ~0x400
  elseif ( temp=="-ignorebitmaps" )
    flags = flags & ~0x80
  elseif ( temp=="-exact" )
    flags = flags | 0x2
  elseif ( temp=="-warn" )
    flags = flags | 0x44
  elseif ( temp=="-merge" )
    flags = flags | 0x1800
    outfile = $1
  elseif ( temp=="-help" )
    Print( "sfddiff: [--version] [--help] [--usage] [--ignorehints] [--ignorenames] [--ignoregpos] [--ignoregsup] [--ignorebitmaps] [--warn] [--exact] fontfile1 fontfile2" )
    Print( " Compares two fontfiles" )
    Print( " --ignorehints: Do not compare postscript hints or truetype instructions" )
    Print( " --ignorenames: Do not compare font names" )
    Print( " --ignoregpos:  Do not compare kerning, etc." )
    Print( " --ignoregsub:  Do not compare ligatures, etc." )
    Print( " --ignorebitmaps: Do not compare bitmap strikes" )
    Print( " --exact:       Normally sfddiff will match contours which are not exact" )
    Print( "                but where the differences are slight (so you could compare" )
    Print( "                truetype and postscript and get reasonable answers). Also" )
    Print( "                normally sfddiff will unlink references before it compares" )
    Print( "                (so you can compare a postscript font (with no references)" )
    Print( "                to the original source (which does have references)). Setting")
    Print( "                this flag means glyphs must match exactly.")
    Print( " --warn:        Provides a warning when an exact match is not found" )
    Print( " --merge outfile: Put any outline differences in the backgrounds of" )
    Print( "                appropriate glyphs" )
  elseif ( temp=="-version" )
    Print( "Version 1.0" )

if ( $argc!=3 || $1=="--usage" || $1=="-usage" )
  Print( "sfddiff: [--version] [--help] [--usage] [--ignorehints] [--ignorenames] [--ignoregpos] [--ignoregsup] [--ignorebitmaps] [--warn] [--exact] [--merge outfile] fontfile1 fontfile2" )

if ( outfile!="" )

Example 3:

#Take a Latin font and apply some simple transformations to it
#prior to adding cyrillic letters.
#can be run in a non-interactive fontforge session.
//Copy those things which look just like latin

//Handle Ya which looks like a backwards "R"

//Gamma looks like an upside-down L

//Prepare for editing small caps K, etc.






The Execute Script dialog

This dialog allows you to type a script directly in to FontForge and then run it. Of course the most common case is that you’ll have a script file somewhere that you want to execute, so there’s a button [Call] down at the bottom of the dlg. Pressing [Call] will bring up a file picker dlg looking for files with the extension *.pe (you can change that by typing a wildcard sequence and pressing the [Filter] button). After you have selected your script the appropriate text to text to invoke it will be placed in the text area.

The current font of the script will be set to whatever font you invoked it from (in python this is fontforge.activeFont()).

Note that if you try to print from a script the output will go to stdout. If you have invoked fontforge from a window manager’s menu stdout will often be bound to /dev/null and not useful. Try starting fontforge from the command line instead.

The Scripts Menu

You can use the preference dialog to create a list of frequently used scripts. Invoke File->Preferences and select the Scripts tag. In this dialog are ten possible entries, each one should have a name (to be displayed in the menu) and an associated script file to be run.

After you have set up your preferences you can invoke scripts from the font view, either directly from the menu (File ‣ Scripts ‣ <your name>) or by a hot key. The first script you added will be invoked by Cnt-Alt-1, then second by Cnt-Alt-2, and the tenth by Cnt-Alt-0.

The current font of the script will be set to whatever font you invoked it from.