Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Glyph E27F (fae-atom) in "Cascadia Code NF" is filled in some areas where it should not be #733

Open
Finii opened this issue May 3, 2024 · 3 comments

Comments

@Finii
Copy link

Finii commented May 3, 2024

Cascadia family version

2404.23

Cascadia family variant(s)

Cascadia Code (the version with ligatures)

Font file format(s)

.ttf (static)

Platform

Linux (me) / Windows 10 (original reporter)

Other Software

Observed when just looking on the outline in Fontforge 20230101, but has been reported to happen (of course) in all applications, mentioned was MS Word 2019, V. 16.0.10406.20006, 32-Bit

What happened?

Some holes in the outline are missing.
This is most likely an "automation" problem when converting the glyphs raw data to a font outline/path.

This shows how the icon looks and is designed in Cascadia Code NF (right) and how it is supposed to look like (left).
The nodes are clearly missing.

image

This has been reported at Nerd Fonts by @TipaRiordan here:

The VF font version has a problematic filling see here:

image

@atauzki
Copy link

atauzki commented May 6, 2024

the rust icon is also filled. I use Cascadia Mono NF.

image

@Logicer16
Copy link

Logicer16 commented Oct 29, 2024

I am also experiencing this issue with "nf-fa-clock" (U+f017) when using Cascadia Code NF:
Image

Expected symbol for reference:
Image

It seems to be an issue in the processing stage. The original looks correct whereas the processed versions are filled in.

@Finii
Copy link
Author

Finii commented Nov 6, 2024

Seems more are affected

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants