Incorporate new ligatures in Fira Code v2, v3, v4 and v5 #276
Labels
Comments
|
Thanks! We'll definitely look into these. |
wopian
changed the title
|
v5 has been released with a few more ligatures |
|
@aaronbell Any ETA? Anybody working on this yet? |
|
Hi. No, we haven't started on this yet. Sorry! We're figuring out next steps for the font :). |
Merged
DHowett
pushed a commit
that referenced
this issue
Feb 9, 2021
This is a significant update to Cascadia Code including a large number of bug fixes as well as updating the font to offer support for Fira Code v5 ligature support. This update supersedes PR #373. Closes #262 - ⏎ added Closes #264 - additional codepoints for control characters added Closes #281 - `!:` and `!.` added Closes #290 - `/\` and `\/` added Closes #301 - `??=` added Closes #324 - ℞ added Closes #327 - `<:>` and other variants implemented via the `calt` refactoring Closes #359 - house added Closes #371 - Added x-height instruction into ttfautohint to control the height of the lowercase. Closes #375 - Completely redesigned quote marks for better recognition Closes #377 - updated hinting to achieve more consistent results Closes #381 - increased height of thetamod Closes #382 - reduced the width of the hooklefts Closes #383 - updated heights on esh, glottalstop, glottalstopreversed Closes #384 - tweaked hinting a little bit. Maybe it'll help :) Closes #386 - added remaining soft-dotting Closes #392 - changed designs of angled quotes (they are now round) Closes #394 - changed former `~=` symbol to a simpler component-based version. Should be less confusing now for Lua / Matlab users. Closes #395 - makes the underline thicker based on font weight Closes #400 - increased size of degree Closes #219 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: Additionally, ss20 includes the oft-unused graphical representations of these codepoints (for fun!): Closes #276 (infinite arrows) Full support for Fira Code's current ligature set (with a few exceptions). Now featuring infinite arrows!!! 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. Closes #329 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. * Not listed – 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. Aside from the above changes, this version also includes many other small updates including spacing, outline quality improvements, and fixing hinting.
|
Thank you 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fira Code v3 was released last month and v4 this week. v2 & v3 includes a large number of new coding ligatures (from the looks of things the ligatures from Fira Code seem to be before v2).
Releases show the added ligatures and what they look like:
https:/tonsky/FiraCode/releases/tag/4
https:/tonsky/FiraCode/releases/tag/3
https:/tonsky/FiraCode/releases/tag/2
v4 features infinite arrow combinations instead of tens of individual ligatures:
The text was updated successfully, but these errors were encountered: