This is a fun, new monospaced font that includes programming ligatures and is designed to enhance the modern look and feel of the Windows Terminal.
I don't think I could say anything to top this one, so here's the release notes for the first version of Cascadia in three years!
Thanks to the tireless work of @PhMajerus, the Cascadia family now supports a whopping 1140 new glyphs covering sextants, octants, large type pieces, eights, sedecimants, quadrants (separated), segmented digits, circles and checkerboards. In addition, the existing block elements have been aligned to fit the same grid as the new characters to make for seamless ANSI art.
See #708, #721, #723 and #727 for more details.
In addition to all of the above characters, the Cascadia family now comes with a native "Nerd Font" variant! It includes the entire set of glyphs as of April 2024 (all 9209 of them), and supersedes both unofficial variants "Caskaydia Cove" and "Delugia Code". Every glyph is metrics-compatible with the rest of Cascadia, so there should be no (or very few?) visual aberrations. @aaronbell is the star of Nerd Fonts for this release!
See #720 for all the details!
This is a "single-issue" bug fix release! Happy holidays!
Shipping from the vaults and crypts of the world, the Cascadia font family returns! Unearthed after centuries shrouded in myth, ḭ͕t͕ co͓mͅe̜̹̻s!
This is a fairly comprehensive (and spooky!) 🐛💀 update resolving many open issues.
NOTE: If you're using the version of Cascadia (Code, Mono) that ships with Windows Terminal, an update will be available in the coming weeks. In the meantime, you can choose to install a new version of the font (which Terminal may ignore) or switch to the powerline face.
Closes #532 👻 - Additional positional variants added
Closes #535 🍂 - Corrected hamza form
Closes #540 🎃 - Dot arrangement corrected
Closes #541 🧹 - Was due to the use of anchors on those glyphs. These have been removed so the glyph can render as spacing.
Closes #542 🌕 - This was partly due to a bug in Harfbuzz. It has been resolved both on the font side (through a different implementation) and in Harfbuzz.
Closes #549 🦸♀️ - Design corrected
Closes #555 💀 - All letter glyphs removed from Arabic Presentation form unicode slots to avoid situations where the glyphs are not behaving as expected.
#543 - uni0615 removed as Cascadia Arabic not intended to support Quranic
Closes #488 🔪 - Finally made the italic https://user-images.githubusercontent.com/8460297/138488419-16f62de9-7797-425c-82e1-6f4384c466a7.png2 AM" src="https://user-images.githubusercontent.com/8460297/138488419-16f62de9-7797-425c-82e1-6f4384c466a7.png">
Closes #436 🧟♀️ - Extended length of Powerline 'caps' to avoid situations where rounding can prevent overlap. This may cause problems if the caps are used next to one another, but that seems an unlikely scenario given what I've reviewed of Powerline styles.
Closes #521 🤖 - enlarged the size of the grave character to make it more recognizable / legible in code.
Closes #524 ☠️ - Added some more differentiation in stroke, and also created more space using hinting.
Closes #525 🧙♂️ - tweaked the braces to be more twisty and create better differentiation from the parens.
Closes #529 🧛♀️ - Changed year :P
Closes #546 👹 - ij no longer masquerading as a mark.
Closes #563 🧟♂️ - corrected locl
feature for proper Serbian rendering
Closes #571 🦹♀️ - corrected overshoot
Closes #572 🕷 - ratio symbol added
Closes #577 🍁 - shifted heights of box drawing lines to better align with block glyphs. Will reduce risk of non-joining forms under certain conditions.
This is a bug fix release for the Cascadia family of fonts, which focuses on naming-related reliability issues and glyph positioning.
U+05B9 HEBREW POINT HOLAM
was positioned incorrectly=>>
, =<<
and friends¹===]
.¹ These are quite subtle; the glyphs just move closer together. I had to stare at it for a solid ten minutes before I realized what was happening!
Arabic (and Urdu) support added (design by Mohamad Dakak) (#84)
Hebrew support added (design by Liron Lavi Turkenich) (#465)
Due to popular demand, we've introduced a more "toned-down" version of Cascadia Italic, which does away with a number of the cursive letter forms. (#468)
/f
/l
/s
and
/r
with typographic feature salt
or ss01
.ƒ
in upright to align better with the standard
f
. In the italic, the ƒ
has been changed to follow the cursive
version. When ss01
is applied, the design of the f
and ƒ
are
swapped, and if the locl
EWE language setting is applied, the f
swaps for a straight descender version (with cursive ƒ
) (#494)=>>
<<=
=<<
and
>>=
(the infinite arrows still work with addition of more equals)rclt
).<$
$>
<$>
ligatures which
we suspect no one will ever notice.This is the first release of Cascadia "Curve", the Italic variant of Cascadia Code.
This is also the first version of Cascadia that is digitally signed.
This is a bugfix release of the Cascadia font family.
Fixes include:
This update to the Cascadia font family brings the following changes:
The full control pictures block has been added (u+2400 to u+2426). For purposes of rendering, the two letter abbreviations have been used instead of the standard three letter abbreviations (#219)
Full support for Fira Code's current ligature set (with a few exceptions). Now featuring infinite arrows!!! (#276)
calt
feature—for those interested, it now uses forward-looking
substitutions instead of backward-looking substitutions and progressive substitution to reduce code. This also
required some redesigning of the greater / lesser related ligatures. Please note, I have also removed all the
obsolete ligatures now covered by the arrows code.There was a mismatch in the font's postscript naming conventions that was corrected. Should now render all weights in Word. Note there is apparently an additional bug in Mac Word's implementation of variable fonts which should be available in an update mid-Feb. (#329)
Reworked the hints for the mod and superscript glyphs so that they're bottom-up rather than top-down. This allows for better bottom alignments.
!:
and !.
added (#281)/\
and \/
added (#290)??=
added (#301)<:>
and other variants implemented via the calt
(#327)
refactoring~=
symbol to a simpler component-based (#394)
version. Should be less confusing now for Lua / Matlab users.Aside from the above changes, this version also includes many other small updates including spacing, outline quality improvements, and fixing hinting.
We realized the Freetype rendering issue documented in #350 had been addressed in neither 2009.14 nor 2009.21. To that end, this is a reissue of 2009.21 with that workaround in place.
So, without further ado (and with a new build pipeline thanks to @madig!):
This update to the Cascadia font family brings the following changes:
-<<
ligature that caused it to overlap itself at certain font weights (#355)