Automatic? component decomposition

Scripting
1

Hello!

I’m building fonts that are quite complex in terms of node and path numbers.

Firstly I’m noticing that otf or ttf exports (when re-imported) don’t seem to keep standard components in tact (eg ÉĔĚÊËĖ etc) and are decomposing. This is is an issue because an /E/ could have several k points in it and I want to keep size down.

Secondly I made a font that is entirely made of components in effort to squash file size. Unfortunately it seems like everything is being decomposed.

What can I do to stop this?

31
311284×1156 319 KB

2

FYI Found some useful info here:
https://forum.glyphsapp.com/t/export-issue-how-many-nodes-are-too-many-nodes/5005/14

@GeorgSeifert “If you set the pixel glyphs to export, the components will not be decomposed and the problem will be gone.”

I set my component glyph to export but it is still being decomposed in the TTF. Any ideas?

cc @Mark

3

You might need the Keep Overlapping Components and Keep Transformed Components (in the Instance Settings).

4

Thanks Georg. Now it keeps components but not at the original size. The component glyph (circle) is to the right.

43
43876×1120 7.18 KB

Decomposed

28
281522×1316 93.9 KB
:

5

can you send me the font?

6

Will do.

7

The export seems to work. But the import fails. Your exported font is fine.

9

Thanks for looking Georg!

10

I fixed the import bug

11

Thank you