glyphsLib: Problems going from UFOs to .glyphs using v3 file format

Using v6.0.0 I’ve been looking at Glyphs v3 file format support.

I see that ufo2glyphs does not currently have an option to output in v3 file format. I created an edited version to test with by adding font.format_version = 3 prior to the font.save section and successfully created a v3 format .glyphs file from a design space file. Is that the correct approach to use to create v3 format files?

Round-tripping using that and then glyphs2ufo produced many differences. Some examples are:

  • postscriptBlueValues, postscriptStemSnapH and postscriptStemSnapV removed from fontinfo.plist
  • styleName in fontinfo.plist changed to Regular for all styles
  • com.schriftgestaltung.weight in lib.plist changed to Regular for all styles
  • public.verticalOrigin added to the lib of all .glif files

Note with the postscript keys, this data does end up in a .glyphs file if it is produced by saving from the Glyphs App - for example blue values end up in Alignment Zones.

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 1
  • Comments: 38 (11 by maintainers)

Commits related to this issue

Most upvoted comments

Just adding in my comment that I’m currently really missing support for converting GlyphsApp “Alignment Zones” into postscriptBlueValues and postscriptOtherBlues and “Stems” into postscriptStemSnapV and postscriptStemSnapH (plus whatever else might relevant here).

There was a lot other stuff in the way. I’m about to continue to work on this.

cannot tell how or where all these _parse… methods are getting called

maybe here?

https://github.com/googlefonts/glyphsLib/blob/10f1b23c207193a6c47c9e86900d3c6dcce04d8b/Lib/glyphsLib/parser.py#L87-L91