googlefonts / googlefonts/fontc

UFO files exported by glyphsapp can store 'export' flag in glyph lib

Open
#1,864 4 comments 0 reactions 0 assignees View on GitHub
correctness crater
Dominant language
Rust
Stars
193
Forks
21
Avg merge
1d 17h
Merged PRs (30d)
65

Description

Specifically we get a glyph lib that looks like,

```


com.schriftgestaltung.Glyphs.Export



```

Currently when we are compiling from UFO we only check the `public.skipExportGlyphs` key, but it looks like we should also be looking at the individual glyphs.

Some quick grepping shows that this appears to be handled on the python side, although in the current source I'm exploring a few glyphs that have this key set are still ending up in the final font when compiled with fontmake:

```
python3 -m ttx_diff 'https://github.com/notofonts/elymaic?4a230cd737#sources/NotoSansElymaic.designspace'
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the Rust UFO compilation path where public.skipExportGlyphs is checked, then compare it with the Python-side handling mentioned in the issue. Use the provided ttx_diff command and the NotoSansElymaic designspace to verify that glyphs with com.schriftgestaltung.Glyphs.Export set to false are excluded from the final font.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.