Cascadia family version
2404.23
Cascadia family variant(s)
Cascadia Code (the version with ligatures), Cascadia Mono (the version without ligatures)
Font file format(s)
Windows Terminal included version (TTF (variable)), .ttf (variable)
Platform
Windows 11 23H2
Other Software
No response
What happened?
First, thank you for your hard work on Cascadia Code 2404.23!
It looks like that some of the following Arabic glyphs look corrupted on all the applications. I was exploring new typefaces using the character map program on Windows while trying to brainstorm an idea for Terminaux (a C# library) while I encountered some corrupted characters at least for the Arabic language. It only happens in the NF and the PL variants.
However, this corruption doesn't happen on large font sizes (43 px and up); only happens on 42 px and lower. When these Arabic characters connect, the corruption increases.
The following characters all suffer from visual graphical glitches (connected or not) that make such letters illegible: (Note that the terminal I-Beam cursor line is not part of the glyph and, hence, not part of the corruption)
| Letter |
Once |
Twice |
Thrice |
| U+063B: ARABIC LETTER KEHEH WITH TWO DOTS ABOVE (ػ) |
 |
 |
 |
| U+0684: ARABIC LETTER DYEH (ڄ) |
 |
 |
 |
| U+0687: ARABIC LETTER TCHEH (چ) |
 |
 |
 |
| U+0688: ARABIC LETTER TCHEHEH (ڇ) |
 |
 |
 |
| U+06AD: ARABIC LETTER NG (ڭ) |
 |
 |
 |
| U+06AF: ARABIC LETTER GAF (گ) |
 |
 |
 |
| U+06B0: ARABIC LETTER GAF WITH RING (ڰ) |
 |
 |
 |
| U+06B1: ARABIC LETTER NGOEH (ڱ) |
 |
 |
 |
| U+06B2: ARABIC LETTER GAF WITH TWO DOTS BELOW (ڲ) |
 |
 |
 |
| U+06B3: ARABIC LETTER GUEH (ڳ) |
 |
 |
 |
| U+06B4: ARABIC LETTER GAF WITH THREE DOTS BELOW (ڴ) |
 |
 |
 |
| U+06B7: ARABIC LETTER LAM WITH THREE DOTS ABOVE (ڷ) |
 |
 |
 |
| U+06B8: ARABIC LETTER LAM WITH THREE DOTS BELOW (ڸ) |
 |
 |
 |
| U+06BF: ARABIC LETTER TCHEH WITH DOT ABOVE (ڿ) |
 |
 |
 |
| U+075E: ARABIC LETTER AIN WITH THREE DOTS POINTING DOWNWARDS ABOVE (ݞ) |
 |
 |
 |
| U+0763: ARABIC LETTER KEHEH WITH THREE DOTS ABOVE (ݣ) |
 |
 |
 |
| U+076A: ARABIC LETTER LAM WITH BAR (ݪ) |
 |
 |
 |
| U+077F: ARABIC LETTER KAF WITH TWO DOTS ABOVE (ݿ) |
 |
 |
 |
| U+08B0: ARABIC LETTER GAF WITH INVERTED STROKE (ࢰ) |
 |
 |
 |
| U+08B3: ARABIC LETTER AIN WITH THREE DOTS BELOW (ࢳ) |
 |
 |
 |
Out of all the glitches experienced by these characters, U+06AF, U+06B0, U+06B2, U+06B3, U+06B4, U+075E, U+077F, and U+08B0 characters are the most affected with their corruption at its worst. However, the normal Arabic characters look fine, such as this:

I suspect that the glyphs for the above characters may not have been generated properly in the final font files.
Cascadia family version
2404.23
Cascadia family variant(s)
Cascadia Code (the version with ligatures), Cascadia Mono (the version without ligatures)
Font file format(s)
Windows Terminal included version (TTF (variable)), .ttf (variable)
Platform
Windows 11 23H2
Other Software
No response
What happened?
First, thank you for your hard work on Cascadia Code 2404.23!
It looks like that some of the following Arabic glyphs look corrupted on all the applications. I was exploring new typefaces using the character map program on Windows while trying to brainstorm an idea for Terminaux (a C# library) while I encountered some corrupted characters at least for the Arabic language. It only happens in the NF and the PL variants.
However, this corruption doesn't happen on large font sizes (43 px and up); only happens on 42 px and lower. When these Arabic characters connect, the corruption increases.
The following characters all suffer from visual graphical glitches (connected or not) that make such letters illegible: (Note that the terminal I-Beam cursor line is not part of the glyph and, hence, not part of the corruption)
Out of all the glitches experienced by these characters, U+06AF, U+06B0, U+06B2, U+06B3, U+06B4, U+075E, U+077F, and U+08B0 characters are the most affected with their corruption at its worst. However, the normal Arabic characters look fine, such as this:
I suspect that the glyphs for the above characters may not have been generated properly in the final font files.