1.061 – Simplified contextual fractions, corrected “onesuperior” kern

The previous release swapped between forms of the fraction bar in contextual fractions. However, this wasn’t supported by most software (#397). So, this simplifies the system to just use one form of the fraction, and morph this to retain legibility between Sans & Mono styles.

It also fixes kerning that disrupted the onesuperior in fractions (#399).

1.060 – Improve contextual fractions in variable font

This release is very similar to 1.059, but will make make contextual fractions work slightly better in macOS & Adobe apps.

See Issue #397 for details.

1.059 – Improved monospace fractions

This release is very similar to the prior release, but it improves arbitrary fractions.

For arbitrary fractions activated with the frac or afrc OpenType features, Recursive now swaps between a split fraction bar in Sans styles (MONO < 0.5) and a solid fraction in Mono styles (MONO >= 0.5). This allows the monospaced arbitrary fractions to maintain clear readability while also maintaining the fixed-width grid of monospaced type setting.

Precomposed fractions (¼ ½ ¾ ⅓ ⅔ ⅛ ⅜ ⅝ ⅞) are still single-unit widths in the Mono styles, and can still be added as the relevant unicodes, e.g. via copy-pasting or by selection from a character palette.

1.057 – Arbitrary fractions, refined superior/inferior figures, refined dots, improved fonts for code

This release has four main upgrades:

1. Arbitrary fractions are now possible! That is, you can still manually enter some common fractions like ¾ or ⅝, but if you turn on the frac OpenType feature, you can also type in fractions like 7/32 or 478/9637. Fractions are slightly large to work well in small text, but if you want fractions that are close to the cap height, you can instead use the OpenType feature afrc with fractions or arbitrary fractions.

2. Superior & inferior numbers have more-consistent positioning & many small refinements to their outlines.

3. Dot accents were slightly misaligned in Heavy styles, and this has been fixed.

4. The Rec Mono for Code fonts have improved metadata which will make them work more consistently on Windows and in various apps. (If you want to customize your own version of Rec Mono for Code, there is now also Recursive Code Config.)

There are other small bug fixes and refinements. Thanks to everyone who helped out by filing thoughtful issues, and special thanks to @benkiel for upgrades to the fraction feature code!

Version 1.054 - fix metadata issues in code-specific fonts

The fonts for code have a few metadata fixes that enable them to work in more Windows software (see #370).

🖳

The main fonts (for desktop & web) are not changed (aside from a bumped version number to keep everything in sync).

UPDATE: release has been updated to fix version numbers in filenames (#374)

Version 1.053 – adds simpler & more-robust code-ligature fonts

This release changes very little in the core fonts.

However, the Rec Mono code-specific fonts have been updated to make their code ligatures work properly in more monospace-only environments, and have gotten a few stylistic sets pre-applied for clear, unambiguous code: a simplified L, Z, l, & f and a more-open 6 and 9.

Note: if you prefer to code without ligatures and/or to have more control over OpenType features, the normal Recursive Mono fonts still have extensive OpenType options as detailed in the main project readme.

Version 1.052 – add DZ, Dz, & dz

This release adds characters DZ, Dz, & dz, which were missing (issue #343).

Interesting: https://en.wikipedia.org/wiki/Dz_(digraph)

Beta 1.051 – “Rec Mono for Code” fonts use `calt` for code ligatures

By popular demand, “Rec Mono for Code” fonts now use the calt OpenType feature for code ligatures.

This should make them work in more contexts, as more apps will understand this older approach.

If you wish to use Recursive Mono to code without code ligatures, you have two options:

1. If using “Rec Mono for Code” fonts: turn off the calt feature.
2. Use the regular Recursive Mono fonts. These won’t display in Roman & Italic themes in most code editors on Mac due to #153, but if a given app doesn’t support basic ligature control, it also probably doesn’t support Italic theming.

In the Desktop & Web fonts, code ligatures are still controlled by the dlig feature so that they are not on by default, as this might confuse many users who aren’t aware of or don’t enjoy code ligatures.

Beta 1.050 – improved fonts for code, corrected stylistic sets, improved STAT table

This release corrects a few issues:

• Rec Mono fonts for code now work more reliably on Windows 10 (#336)
• Rec Mono fonts for code are fixed to utilize the correct forms of glyphs in more apps, including iTerm2 & MacVim (#335)
• Stylistic sets were misaligned between the font and the documentation. The simplified 1 is now available in ss11 and the slashed 0 in Sans is available in ss20, as described in the project README.
• The Stylistic Attributes (STAT) table has been improved in the variable font, which may improve its usability in certain apps, especially on Windows (#337). Thanks, @benkiel!

Documentation in the release itself has also been improved. In particular, there is advice on performant web font usage in the README.md within Recursive_Web.

Beta 1.047 - small cursive-swapping fix

This contains all the same updates as 1.046, but fixes behavior of cursive substitution for l and i in Sans styles (they were inconsistent with other substitutions along the CRSV axis, and not possible to turn off at `CRSV 0, slnt -14 to -15).