googlefonts / googlefonts/fontc

off-by-ones in mark pos rule deltas

Open
#1,834 1 comment 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 is evident, for instance, in Kablammo. We expect to sometimes have some off-by-ones in other places, but we don't currently allow any in otl-normalizer output.

- if possible, we should just figure out what we're doing differently in the math
- if that's too annoying, we can fix some off-by-ones in the normalizer output?

```
python3 -m ttx_diff 'https://github.com/Vectro-Type-Foundry/kablammo?cccc120d23#sources/Kablammo.glyphs'
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by running the provided ttx_diff command against the Kablammo source and inspect the reported mark positioning rule deltas. Compare the differing math or normalizer output to determine whether the underlying calculation or only the emitted off-by-one values should change; done means the discrepancy is resolved without allowing unintended off-by-ones in otl-normalizer output.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.