googlefonts / googlefonts/glyphsets

Glyphset coverage calculation: Check for *shapable* character rather than relying on cmap table

Open
#178 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
115
Forks
20
PR merge metrics
No merged PRs in 30d

Description

OT specs theoretically allow character composition on-the-fly from a base glyph and combining marks plus anchors without encoded characters being part of the font (`a`+`¨` is sufficient, `ä` needn't be present).

Glyphset coverage calculations currently rely on encoded characters to be present, but I'd like to widen the calculation to check for characters that are _shapable_, not necessarily present in the `cmap` and `glyf` tables.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.