FontLab Studio 5 updates: 5.1.5 Mac & 5.2.2 Win

We have officially approved the most recent v5714 builds of FontLab Studio 5 for general release: these will be the official 5.1.5 Mac and 5.2.2 Windows releases. Compared to the previous 5.1.4 / 5.2.1 releases, this fixes 40 bugs, including 24 bugs present on both platforms, 7 Mac-only issues, and 9 Windows-only issues.

We strongly recommend the new versions for all 5.1 / 5.2 users. We also suggest them for 5.0.x users; although there are a few bugs introduced in 5.1 / 5.2 that are not yet fixed, overall we think these versions are better than 5.0.4 and earlier.

Mac users, please read the release notes for install details as well! Then download:

Mac Install Info

Unfortunately, due to some technical issues, the Mac installer and app are not “code-signed,” so Mac OS X sees it as coming from an “unidentified developer.” We realize this is not ideal, but we thought it would still be better to give you these bug fixes than to sit on the installer until we sort out the install issue. Thanks for understanding.

FontLab Studio Mac now has a user interface localized in seven languages! No longer just English—also French, German, Spanish, Portuguese, Chinese and Japanese. You can also override the automatic language selection to get a different UI language.

To launch the Mac installer (and the app) the first time, please:

  • Right-click (Ctrl-click) on the installer (or the installed application) in the Finder and choose “Open.”
  • Click on “Open” in the dialog box that appears.
  • You’ll only need to do this once to install, and once again on the app. After this it will just launch normally.

Windows Install Info & Python

(Updated 14 March 2016)
Since the release of 5.2.2 for Windows, we have encountered an compatibility issue with the newest Python 2.X, version 2.7.11. Version 5.2.2 will not launch with this version of Python installed, without extra measures. There are two possible solutions, below. (Note: you do not need Python installed at all to run FontLab Studio 5; it is just that if you do have it installed, this can be an issue.)

  • Note that it must be a 32-bit version of Python installed. FontLab Studio 5 will not work with a 64-bit Python. (32-bit Python will run fine on a 64-bit version of Windows.
  • One option is to install Python 2.7.10 instead.
  • The other option is to do the following steps, to edit the environment variables via the System Properties dialog:
    • Windows Key + X
    • System
    • Advanced system settings
    • Environment Variables…
    • and add a PYTHONHOME variable with value of “C:\Python27”
    • python01

Changes & Bug Fixes in 5.1.5 / 5.2.2

There was one major code change. When generating OTF fonts, we no longer use the Adobe AFDKO code to generate the name table and OS/2 table; instead we rely on FontLab’s own code, which was already being used for these tables in TTFs. This change yields more consistent results between TTF and OTF, ensuring user-defined info shows up in the font regardless of format, and avoids surprise default results that are not visible in the FontLab interface.

Also, “language” lists were updated in “Additional OpenType names” tab of Font Info for Windows and Macintosh platforms in accordance with http://www.microsoft.com/typography/otspec/name.htm.

Bugs which were both introduced and fixed during the development of this release are not listed.

Special thanks to Lucas de Groot for reporting at least 20 of the bugs we fixed.

Mac & Win dual-platform bugs

    1. The Preview panel doesn’t update when you browse through fonts in Font Info (worked in 5.0.4)
    2. Generating Unicodes using a .nam file fails on last glyph in font
    3. Underscore char not supported in the Family Name
    4. Component numbering display bug
    5. Generate Instance causes PFM Default Character field in Font Info to become empty
    6. Pasting from MM to single master glyph pastes all masters, not just the active layer
    7. [FATAL] Compiling Verdana Regular GPOS ‘kern’ feature fails (worked in 5.0.4)
    8. Underline and strikeout positions (and thickness) are changed on export to OTF
    9. CFF subroutinization nesting problem can cause glyph rendering problems in some fonts
    10. Disappearing outlines in one master of MM fonts
    11. Wrong tooltips in TT Hinting Options > Zones, and top zone can’t be changed after being set
    12. Metrics Window contextual menu issues
    13. Blue class kerning indicators not visible in Kerning Table of Metrics Window
    14. Metrics undo is applied only to the base component of composite glyphs
    15. “Digital signature” and “Trace Options” sections disappear from “Preferences” (Options) dialog after performing “Reset
    16. options to defaults” command
    17. Slanting in the Actions dialog does not work with decimals (fractional values)
    18. OTF only: export of “name” table loses non-ASCII characters, OS/2 table inserts default values for blanks,
    19. Add -Regular in auto-generated PS FontName and Full Name
    20. Using tab key between Metrics windows fields disables further glyph editing afterwards
    21. Pasting from EPS scales inconsistently
    22. Component shift doesn’t work in Generate Glyphs dialog
    23. Trying to generate a font containing 65536 glyphs causes lock up instead of warning
    24. Hidden classes sometimes get deleted during re-ordering

Mac-only issues

    1. Font create date not editable and auto-set to current date/time in OS X 10.9+
    2. Printing fails on OS X 10.9+ (Out of memory error)
    3. Copy Font Info dialog: missing Select All/None buttons
    4. Underscore and digits are not allowed in PostScript Name
    5. Menus disappear if user chooses a Workspace with a non-ASCII character; app must be restarted with Control pressed to fix
    6. Wrong Type 1 hinting rasterizers in Hinting Preview
    7. Applying any saved workspace using the Window>Workspace menu shifts all toolbars

Windows-only issues

  1. Customized vertical global guideline colors lost when .vfb is saved and reopened
  2. Temporary files are not deleted when font generation fails (causes font generation problems afterwards)
  3. Typing very long Metrics preview strings can cause crash
  4. Transformation “Mirror” buttons require two clicks
  5. Menu shortcuts do not work when the mouse cursor is above a beveled button in a panel
  6. Switching between masters using keyboard shortcut doesn’t update Masters and Axis panels
  7. The Meter panel doesn’t stick around when you close and open glyphs
  8. Bold effect in the Actions dialog rounds corners even when rounding option is off
  9. Distance/angle in the Meter panel doesn’t show info

Tags: , , , ,

Trackback from your site.

Thomas Phinney

Thomas Phinney is President of FontLab. Previously he worked at Extensis (web fonts and font management tools) and Adobe (as product manager for global fonts and typography). Thomas is also a type designer, teacher, writer, and consultant on fonts and typography. He has been consulted by Apple, Adobe, Microsoft, Oxford University Press, a “big three” US auto maker, the US Treasury Department, and PBS “History Detectives,” among others. He teaches type design with Crafting Type and has been a repeat guest lecturer for MA Typeface Design at the University of Reading. Since 2004 he has been a board member of ATypI, the international typography association. His typeface Hypatia Sans is an Adobe Original with over 3000 glyphs per font.

Comments (21)

  • Sean Cavanaugh

    |

    The Mac installer linked above has a modification date of April 30, 2013 and installs version 5.1.4 4868.

    Reply

    • Thomas Phinney

      |

      Agh. I got tripped up by our complex redirects and site structure. But it should be fixed now.

      Reply

  • Nikola Kostic

    |

    How do I install the Windows update? It doesn’t do it automatically.

    Reply

    • Nikola Kostic

      |

      Oh sorry, I forgot to “run as administrator”. It works.

      Reply

      • Philipp Steinkellner

        |

        the mac version immediately crashes on startup on 10.6.8 (5.1.4 was fine):

        Exception Type: EXC_BREAKPOINT (SIGTRAP)
        Exception Codes: 0x0000000000000002, 0x0000000000000000
        Crashed Thread: 0

        Dyld Error Message:
        Library not loaded: /Library/Frameworks/Python.framework/Versions/2.7/Python
        Referenced from: /Applications/FontLab Studio 5.app/Contents/MacOS/FontLab Studio 5
        Reason: image not found

        Reply

        • Thomas Phinney

          |

          I have updated the install instructions: People on OS X 10.5 and 10.6 will need to install Python 2.7 (see link above).

          Reply

          • Philipp Steinkellner

            |

            thank you! now it works!

            Reply

  • Kimmy

    |

    I didn’t see it on there but are you guys planning to fix the issue of working with a Wacom tablet? Currently every time you lift the pen (particularly to use the keyboard for a key command) it makes the screen scroll up. After doing this 3 times the letter is completely hidden at the bottom of the glyph window. I’m not sure if it’s a FLS or Wacom issue but it sure does get annoying after awhile 🙂

    Reply

    • Thomas Phinney

      |

      Sorry, no we haven’t been able to address this as yet. I can’t tell you who to blame, but it used to work, and was broken with the latest Wacom drivers. However, we have conflicting info on whether the needed older driver can be installed on latest versions of Mac OS.

      We don’t currently have plans for another dot release, as we are full steam ahead on FontLab VI. I understand how irksome it must be for you, however. 🙁

      Reply

      • Kimmy

        |

        Aha, I see. I use my tablet about 99% of the time, and while it’s a drag to have to deal with the scrolling issue, it’s not the end of the world (I’ve learned to deal with it.)

        Thanks again!! I will keep my hopes up for a fix from someone someday!!

        Reply

    • Mike Speke

      |

      Kimmy, the Wacom problem is not a Fontlab issue, it’s an issue between Apple & Wacom. And they are really taking their time to fix it (not yet). Go back to CC 2014 instead of 2015.

      Reply

  • Guang Leung

    |

    Can I get a copy of documented FontLab Python Scripting Reference? It means a lot to our little design team to make time-saving scripts.

    Reply

  • Hans Samuelson

    |

    Hi, I still suffer from the no 25 issue in the list above. The creation date is set to ‘ 201-11 17’ (yes; a space + three number year). Also, the font creation year exports as 1944. This happens in the 5714 build as well.

    Reply

  • Henning Wagenbreth

    |

    Hi! I just tried to install the latest Fontlab 5.1.5 on OS X 10.11.1
    The installation went well: »installation successful«, but at the first launch of the program, the starting panel appears for less than half a second, disappears and that was it. Nothing opened. Does anyone have the same problem?

    Reply

    • Rüdiger Jung

      |

      Hi,
      I have the same problem as Henning Wagenbreth. I tried with 10.7.x, 10.9.x, 10.11.x always the same problem as described above… Installing python (necessary for 10.5.x and 10.6.x) doesn’t change anything… What can I do?!

      Reply

  • Julien

    |

    Hello, I have the same problem than Kimmy, with the wacom tablet. In fontlab glyph window, it makes the screen scroll up. It’s totally annoying. My system: Mac os 10.11.2, fontlab 5.1.4, wacom latest driver (can’t install previous driver on mac os 10.11). Any solution please? Thanks a lot. J

    Reply

  • Julien

    |

    Sorry Fontlab 5.1.5, not 5.1.4 (the last one also, so). Thanks

    Reply

    • Thomas Phinney

      |

      It seems that the compatible driver version(s) can’t be installed on 10.11 and 10.12. We don’t anticipate having a fix for 5.x, but so far we have seen VI working well with such drivers. This is just one of the many advantages we have in VI by building on top of a modern development framework.

      Reply

  • Thomas Phinney

    |

    It seems that the latest (mid and late October 2016) driver updates from Wacom solve the problem! These work fine on latest OSes and with latest tablets.

    Reply

Add a comment