I would love to see TT instructions made on Glyphs not be lost when exporting to .ufo. Is this something possible with the current UFO 3 format?
It is not really possible (in a useful way) to store hints in an ufo. I could store it as private data, but that can’t be used anywhere.
I was just thinking on the possibilty of using Glyphs to do the hinting work and store data as ufo. Of course it will require to use Glyphs to build the font but would be really cool if fontmake can use this data too.
As soon as fontmake will be able to compile the hints, it can read the data from .glyphs file via glyphLib. So no reason to convert to .ufo now.
Hi Georg,
I am going to work for a designer that works in RoboFont and hint the fonts in Glyphs.
Therefore it would be helpful to store the Hinting data in the UFO instances.
UFO can store PostScript aswel as TrueType data.
Apparently RoboFont, using Fontmake to produce fonts, would be able to produce fonts with hinting data. But I can not test that, since the hints are not saved into the UFO file.
This would make it possible, to deliver UFO’s next to hinted Glyphs files, that might be able to be customised later. (think of switching stylistic sets or reduce glyph sets)
Since Glyphs is the the absolutely best editor to hint fonts (you can use this), I might even be abel to convince others to work in a RoboFont Glyphs hybrid workflow.