Skip to content
v2111.01
Compare
Choose a tag to compare

This is a "single-issue" bug fix release! Happy holidays!

  • The brace ligatures in the italic style will no longer look totally hilarious and terrible (#595)
v2110.31
823c699
Compare
Choose a tag to compare

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.

Arabic bugfixes

  • Closes #532 👻 - Additional positional variants added
  • Closes #535 🍂 - Corrected hamza form
  • Closes #540 🎃 - Dot arrangement corrected

Screen Shot 2021-10-22 at 9 15 47 AM

  • 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

Screen Shot 2021-10-22 at 9 14 04 AM

  • Closes #555 💀 - All letter glyphs removed from Arabic Presentation form unicode slots to avoid situations where the glyphs are not behaving as expected.

Arabic changes

#543 - uni0615 removed as Cascadia Arabic not intended to support Quranic

Other bug fixes

  • Closes #488 🔪 - Finally made the italic www ligature have the proper number of ws.

Screen Shot 2021-10-22 at 9 13 02 AM

  • 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.

Screen Shot 2021-10-22 at 9 17 34 AM

  • Closes #521 🤖 - enlarged the size of the grave character to make it more recognizable / legible in code.

Screen Shot 2021-10-22 at 9 19 52 AM

  • Closes #524 ☠️ - Added some more differentiation in stroke, and also created more space using hinting.

Screen Shot 2021-10-22 at 9 20 25 AM

  • Closes #525 🧙‍♂️ - tweaked the braces to be more twisty and create better differentiation from the parens.

Screen Shot 2021-10-22 at 9 20 58 AM

  • Closes #529 🧛‍♀️ - Changed year :P
  • Closes #546 👹 - ij no longer masquerading as a mark.
  • Closes #563 🧟‍♂️ - corrected locl feature for proper Serbian rendering

Screen Shot 2021-10-22 at 9 22 40 AM

  • 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.
v2108.26
f91d08f
Compare
Choose a tag to compare

This is a bug fix release for the Cascadia family of fonts, which focuses on naming-related reliability issues and glyph positioning.

Bug Fixes

  • #500 - An unused "Italic" axis in the non-Italic version of the font caused tools like Visual Studio Code to exclusively display in Italic. Whoops!
  • #552 - U+05B9 HEBREW POINT HOLAM was positioned incorrectly
  • Re-enabled ligatures for =>>, =<< and friends¹
  • An adjustment has been made to ligature substitutions to ensure that they activate properly, as in ===].

¹ 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!

f1a0b0e
Compare
Choose a tag to compare

Features

  • Arabic (and Urdu) support added (design by Mohamad Dakak) (#84)

    • See the Arabic features PDF for the exciting new Arabic ligature
      functionality used in Cascadia Code that gives the font greatly improved
      readability and feel more more akin to a text typeface.
    • Don't want all that? Don't worry, Cascadia Mono will house a normal
      version of Arabic.
  • 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)

    • Entry and exit strokes across the italic lowercase have been rounded
      to better achieve the fun / playful design language that we intended
      for the italic. Other skeletons have been modified as necessary.
      Cyrillic has also been updated for better consistency with the new
      design.
    • You can now activate the original cursive versions of /f /l /s and
      /r with typographic feature salt or ss01.

Changes

  • We have adjusted the slant on all of the italic letters to make sure it's
    consistent (#470)
  • Italic Only: #507 - bar and broken bar will now stay upright for better clarity
  • Changed design of ƒ 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)
  • Fixing a bug in the ccmp feature file and added ccmp to the feature
    set in the build script.
  • Deleting the (unused) liga feature file
  • Vika has reviewed and improved some forms in Cascadia Code upright.
  • Greek lowercase has been updated per feedback from Gerry Leonidas to
    be more cohesive (No longer a mix between a "Monday" and "Friday" font.
    All Friday, all the time!)
  • #422 - Bitcoin glyph added
  • #427 - FFFD glyph added
  • #418 - top bar corrected
  • #433 - hinting corrected to ensure alignment
  • #435 - adds consistent ligature form for =>> <<= =<< and
    >>= (the infinite arrows still work with addition of more equals)
  • #443 - ligature now ignores (*) scenario
  • #454 - adds ignore to prevent equal_equal ligature from showing up
  • #467 - Not specifically sure of the problem here, but suspect that it will
    be fixed with this - update.
  • #477, #478, #479, #480 - interpolation issues fixes in a lot of ligatures
  • #481 - JetBrains enumerates fonts weird. We've modified the internal naming
    so that it will register Cascadia Code correctly. Also aligned postscript
    naming with Google's recommendation, so will show up as "Regular" instead of
    "Roman".
  • General improvement of weight balancing
  • Weight of lowercase rounds reduced in the Bold weight in Cascadia Code.
  • Weight of Capital stems increased in Extralight weight in Cascadia Code.
  • Tweaked weight of ogonek in ExtraLight.
  • Added a localized form for ij and IJ should a user chose to use those
    codepoints and want an accented version.
  • Split fraction bar at heavier weights to improve clarity of fractions.
  • Adjusted standard box drawing characters to align with GDI metrics, and added
    a complete set of DWrite-specific ones that align with sTypo (using rclt).
  • Ironed out some tiny inconsistencies in the <$ $> <$> ligatures which
    we suspect no one will ever notice.
  • Fixed centering of braces and some hyphens.
  • Fixed inconsistency between semicolon/colon and period weight in bold. Also
    fixed slight differences in hyphen-like glyphs in bold. You're as surprised
    as we are.
  • Increased weight of underscore in bold.
  • Adjusted weighting of Ɫ.
  • Changed design of commaaccent, commaaccentmod commaturnedabove and commaabove
    to be more distinguishable (following design of quotes).
  • Increased height of βδθλ to align with the ascender height. They were too low
    before.
  • Fixed descents of various greek lowercase glyphs that were inconsistent.
  • Modified ξ weighting.
  • Felt ligated, might edit later.
  • Tweaked ªºⁿʷʸᶿᶻ⁰¹²³⁴⁵⁶⁷⁸⁹ in imperceptable ways.
  • Corrected some additional interpolation bugs
v2105.24
82b5b9b
Compare
Choose a tag to compare

This is the first release of Cascadia "Curve", the Italic variant of Cascadia Code.

Cascadia with Italics

This is also the first version of Cascadia that is digitally signed.

Compare
Choose a tag to compare

This is a bugfix release of the Cascadia font family.

Fixes include:

  • Closes #406 - updated anchor type to lock with the other equals-related ligatures
  • Closes #408 - corrected component used for glyph to align with Unicode
  • Closes #412 - updated locl features removing iacute_j ligature and Catalan substitution
  • Closes #414 - increased overlaps of middle glyph for arrow ligatures
  • Closes #415 - reduces width of macronbelow
  • Closes #416 - rolls back name ID 4 modification as JetBrains cannot process it correctly
  • Closes #428 - rolls back variation of the underline to prevent MVAR table generation
  • Repositioned tilde in related ligatures. Previously it was higher than the standard one.
  • Added missing vietnamese anchors on acute and grave (futureproofing).
  • Corrected / made consistent greater & less positioning in </> and <$> related ligatures.
  • Otherwise reviewed hinting
8f5eea8
Compare
Choose a tag to compare

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)

    • image
    • Additionally, ss20 includes the oft-unused graphical representations of these codepoints (for fun!)
    • image
  • Full support for Fira Code's current ligature set (with a few exceptions). Now featuring infinite arrows!!! (#276)

    • image
    • This involved a full refactoring of the 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.

New Glyphs

  • ⏎ (#262)
  • additional codepoints for control characters U+21B2, U+2771, U+2770, U+2423 (#264)
  • U+211E ℞ (#324)
  • U+2302 HOUSE (#359)

New Ligatures

  • !: and !. added (#281)
  • /\ and \/ added (#290)
  • ??= added (#301)
  • <:> and other variants implemented via the calt (#327)
    refactoring

Changes

  • Added x-height instruction into ttfautohint to control the (#371)
    height of the lowercase.
  • Completely redesigned quote marks for better recognition (#375)
    • image
    • Note: this only applies to curved/smart quotes
  • updated hinting to achieve more consistent results (#377)
  • increased height of thetamod (#381)
  • reduced the width of the hooklefts (#382)
    • image
  • updated heights on esh, glottalstop, glottalstopreversed (#383)
    • image
  • tweaked hinting a little bit (#384)
  • added remaining soft-dotting (#386)
    • image
  • changed designs of the angled quotes (#392)
    • image
  • changed former ~= symbol to a simpler component-based (#394)
    version. Should be less confusing now for Lua / Matlab users.
  • made the underline thicker based on font weight (#395)
    • image
  • increased size of degree (#400)

Aside from the above changes, this version also includes many other small updates including spacing, outline quality
improvements, and fixing hinting.

744b23f
Compare
Choose a tag to compare

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!):

  • We have implemented a workaround for a freetype rendering issue that resulted in chunky rendering for certain glyphs (#350)
  • This bugfix release to the Cascadia family of fonts fixes diacritic positioning for the Salishan languages.
716c6e6
Compare
Choose a tag to compare

This update to the Cascadia font family brings the following changes:

  • Cascadia now has support for the Salishan languages of the Pacific Northwest and other coastal scripts!
  • We've fixed an issue in the -<< ligature that caused it to overlap itself at certain font weights (#355)
  • We remastered mark positioning for glyphs with existing diacritics for improved design for letters with multiple diacritics above
  • We have implemented a workaround for a freetype rendering issue that resulted in chunky rendering for certain glyphs (#350)

An image depicting some of the new glyphs in Cascadia

v2008.25
678eea9
Compare
Choose a tag to compare

This update to the Cascadia family of fonts brings the following changes:

  • We are now generating static TTFs for every named variant
    • These static instances will be hinted using ttfautohint, and so will look different than the variable font at small and intermediate point sizes
  • We've temporarily stopped shipping variable OTFs due to some concerns about overlapping and psautohint
  • The heaviest weight of Cascadia has been made a little lighter
  • We have aligned the Powerline glyphs and the box-/line-drawing glyphs better to their metrics and to the letter glyphs
  • Diacritic anchors have been added to all alphabetic characters (#282, #330)
  • The font now ships with decomposed fi and fl ligatures
  • The horn combining diacritic has had its weight fixed somewhat for Bold
  • Primes have been redesigned to give them a more "angled" feel (#294)
  • Acute and grave have been given additional weight to help differentiate them from dot (#268)
  • The contextual alternate for x used to signify hexadecimal numbers has been disabled (#285)