googlefonts / googlefonts/fontc
Potential for mistaken retention of .table files
Open
- Dominant language
- Rust
- Stars
- 193
- Forks
- 21
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 60
Description
If we emit ir - required for incremental compilation - and we compile first a font that has a table, then a font that doesn't, I believe we could mistakenly merge the leftover table file into the second font.
I believe that if we are emitting ir:
* If static metadata changed we should delete *.table
* If features changed we should delete gsub and gpos .table
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.