daltonmaag / fontgardener Goto Github PK

Some sets can use glyphs from other sets as components (i.e. "A-cy" may use "A"). Fontgardener should

1. on import: also import glyphs used as components by glyphs on the import list, into their appropriate set
2. on export: also export glyphs used as components by glyphs on the export list.

Glyphs used in substitutions are left out for now and have to be manually placed on the (im|ex)port list, until the tool actually has a better idea about OpenType Layout.

Use case: a designer wants to work on e.g. the Cyrillic set but needs parts of the Latin set for it.

If the indirectly imported glyphs aren't in a set yet, they'll land in the same set as their users. This may not be what one wants in some instances, so later, glyphs need to be able to move.

Maybe there should be an option to not do this on import, but for now, undoing those changes manually seems ok to me.

The following import of Noto Sans will import Bold Italic incompletely, only when running it a second time is the import complete:

> fontgardener new NotoSansDemo2.fontgarden

> fontgardener import NotoSansDemo2.fontgarden --set LatinGreekCyrillic --glyphs-file $env:TEMP\NotoUFOs\LatinGreekCyrillic.txt $env:TEMP\NotoUFOs\NotoSans-MM\NotoSans-Bold.ufo $env:TEMP\NotoUFOs\NotoSans-ItalicMM\NotoSans-BoldItalic.ufo

Currently, glyph data is organized into sets into sources into layers into glyphs, sort of extending the UFO data model of putting glyphs in layers.

1. It works, but introduces some inelegance when e.g. you want to export glyphs and want to determine, per layer, which other glyphs you have to also export because they're used in composites.
2. It leads to a lot of files on disk.

I wonder if there could be a more elegant data structure where e.g. you keep the sources with all glyphs and have a separate glyph->set mapping in a regular HashMap<NameOfGlyph, NameOfSet> :thinking_face:

Or even turn the relation on its head and have glyphs contain set name, sources and layers, sort of like Glyphs.app and FontLab 7 do.

You could even keep the structure on disk if desired and do the head-turning internally.

Not just glyph names.