[varLib] warn when using rvrn substitution for glyphs without codepoint?
See original GitHub issueGiven how rvrn
is misdesigned to go first instead of last, it can as far as I understand only sensibly be used for glyphs with a Unicode codepoint, i.e. something that is not the result of another substitution. Maybe varLib should log a warning about this when encountering an input glyph without a codepoint and suggest to either use rclt
or manually write out the variation substitution chains in the feature file?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Why does changing the encoding not work in pdfTeX for ...
To me, reencoding is replacing glyph->codepoint mapping which is in Type1 font by default with new glyph->codepoint mapping, where order of ...
Read more >fonttools/NEWS.rst at main
A library to manipulate font files from Python. Contribute to fonttools/fonttools development by creating an account on GitHub.
Read more >Source code for fontTools.subset - Read the Docs
--no-harfbuzz-repacker Always use the pure-python serializer even if uharfbuzz is ... Substitute, indices) # Now drop rules generating glyphs we don't want ...
Read more >FontLab 7 Release Notes Part 4
The Alternative names use hyphens more often than the Friendly names. ... red lines in Font window glyph cells when no Unicode codepoint...
Read more >unicode - Is there a "glyph not found" character?
No, there is no “glyph not found” character. Different programs use different graphic presentations. An empty narrow rectangle is a common rendering, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Already done in a certain PR in a certain secret repo.
While I agree that
rvrn
is close to useless for real use, I have since learned that its mere existence is due to the specced behavior: without early processing (“before anything else”), there would be no need forrvrn
at all, as the remaining behavior can be done viarclt
orrlig
. (Paraphrasing John Hudson, who explained it to me patiently while I was still foaming with rage 😃 )That said, maybe indeed such a warning would be good.
(Note that
rclt
still doesn’t work in most Adobe apps, another thing worthy of some foaming rage.)