googlefonts / googlefonts/fontc

difference in handling of metric values in some glyphs sources

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

Description

This comes up with 'underlineThickness', in Playfair.glyphs.

What is particularly interesting in this case is that the diff goes away if we first convert from glyphs to designspace, and _then_ compile, so it seems like possibly some interaction between fontmake/ufo2ft and glyphslib?

Repro:

```
python3 -m ttx_diff 'https://github.com/googlefonts/Playfair?a49f9f9dc9#sources/Playfair.glyphspackage'
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by running the provided ttx_diff command against the Playfair glyphs source and inspect the underlineThickness difference. Compare the direct glyphs compilation with the glyphs-to-designspace-then-compile path, focusing on the reported interaction between fontmake/ufo2ft and glyphslib. Done means identifying and correcting the differing metric handling, with the reproduction no longer showing a diff.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
compilers, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.