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
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.
This makes it easier to use the mk fragment with fonts that need a build
step, like new liberation-ttf.
While here switch some fonts using post-install unnecessarily to do-install
(Committed at the same time as it wasn't tested separately)
No PLIST changes to the packages/build breakage, so no changes expected
to the packages.
2009.22
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.
2009.14
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)
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)
The Cascadia font family is now available with a variable weight axis ranging from extra-light (200) to bold (700).
In addition, the following bugs were fixed and changes were made:
Changes
The double-equals ligature == has been updated to improve visual clarity (image)
The diacritics on IJacute are no longer malformed
We've introduced a set of compatibility features to improve the rendering of powerline glyphs in legacy GDI applications
