We need to parse the file .glifs (or another who contains the names of characters) to automate creation iconic font. Someone has this experience?
Glyphs file is actually a text file (or can be opened and modified with a text editor), if that’s what you’re asking.
There is actual documentation for it in the works. But for the time being, I simply recommend opening it in a text editor, I think it is pretty self-explanatory for the largest part.
It’s self-explanatory, really, and this just made me curious why Glyphs use its own ‘readable’ font format instead of UFO?
One reason might be that a glyphsfile can contain multiple master, ufo can not.
And .ufo file are two to three times bigger. But jakob is right, the main reason is the missing Multiple Master support.
Oh, OK, I wasn’t aware of that - thanks!
So, anyone has tried to deserialize the .glyphs file?
What do you mean by that?
Glyphs files are text files, formatted based on the plist format. There is a spec: GlyphsSDK/GlyphsFileFormatv3.md at Glyphs3 · schriftgestalt/GlyphsSDK · GitHub
And there is glyphsLib, an python library that reads and writes .glyphs files.
What do the node type codes, c, l, o, q mean? I didn’t see that in the file you posted above (from Dec, '21)
OK, from looking at some source code for that python parser, I think it’s
C = CURVE
Q = QCURVE
L = LINE
O = OFFCURVE
S (if added) = SMOOTH, otherwise the node is SHARP.
I found more information here: Glyph Interchange Format
describing the meaning of those point types.