Open adrian5 opened 3 years ago
I believe all of those glyphs are being displayed with fallback. Will add to the backlog of items to work on :)
The "ballot cross" (✗, u+2717) is also missing, while the checkmark (✓, u+2713), which kind of goes with the cross, has been implemented.
When combining the check and the cross to use as "yay" or "nay", it causes alignment problems (or truncation, depending on the app used) because Windows falls back to some other font which has a different width than Cascadia.
Cascadia family version
v2102.25
Cascadia family variant(s)
Cascadia Mono (the version without ligatures)
Font file format(s)
.ttf (static)
Platform
Linux (fontconfig 2.13.93)
What happened?
I'm not sure if it's an issue on my side, but the Crossmark symbol (❌) doesn't appear to be implemented in the font. It's sometimes used in modern terminal applications (also prominently in GitHub markdown as
:x:
) to signify errors . To that end, it's useful to have.The similar Multiplication X (✕) and Heavy Multiplication X (✖️) show up for me, though they don't fit in well with other glyphs — I'm not sure if they are coming from a fallback font on my system.