Junicode version 2.222

The changes in Junicode 2.222 are mostly to support a new utility, pua2ot, which converts text containing Medieval Unicode Font Initiative (MUFI) characters encoded in the Unicode Private Use Area (PUA), MUFI entities, or both to standard Unicode styled with Junicode’s OpenType features. The result of this conversion is text that is far more accessible than the original: the utility may help with compliance with EU acessibility regulations, the W3C Web Content Accessibility Guidelines, and the like. Pua2ot is a JavaScript utility that comes in three flavors: a GUI version (drag the file pua2ot/gui/pua2ot-gui.html into any up-to-date browser), an embedded version (which will convert text in the body element of any web page it is embedded in), and a Node module (enabling users to write their own utilities). The utility, with documentation, is in the directory pua2ot, and each flavor comes with demo and test files. Because most users will not need this utility, it is not included in the .zip archive, but it can be downloaded from the repository directory pua2ot. Be sure to create a directory pua2ot/fonts, and copy the woff2 versions of the Junicode VF variable font into it before trying out the utility.

Junicode version 2.220

This version adds rules in rlig (Required Ligatures) to duplicate the functionality of hlig (Historic Ligatures) using U+200D ZERO WIDTH JOINER. The feature may be useful to users who make extensive use of hlig, which needs to be turned off wherever it is not needed: using ZWJ can drastically reduce the amount of tagging needed in a file. The feature also duplicates some digraphs (e.g. æ, œ) as ligatures, which can be searched by their elements (e.g. "ae" for æ), and combining marks may be centered over the elements instead of the whole glyph (a feature that some medievalists have needed). Anchors have been added for some glyphs that lack them, and some glyphs that have mistakenly been treated as digraphs have been reclassified as ligatures (treated in hlig).

Note that feature ss17 (Rare Digraphs) is now deprecated: use ZWJ to form ligatures equivalent to the covered digraphs. ss17 will be removed from Junicode in version 2.225.

Junicode version 2.219

Version 2.219 revises feature ss20 so that it never causes bad formatting of combining marks (it can now be on for the whole document), adds several ligatures (especially for representing Norse abbreviations for dróttinn), and adds anchors to several glyphs.

Junicode version 2.218

This release fixes a bug that prevented some contextual kerning rules from working properly.

Junicode version 2.217

Version 2.217 of the font adds top anchors for any Greek letters that lack them so that combining marks other than the standard Greek marks can be added. It also adds to cvNN (Character Variant) features support for "Symbol" shapes of Greek β, θ, φ, π, κ, ρ, and ε so that these can be substituted for an entire document with a single command. For details, see the Junicode Manual § 4.3.1.

Junicode version 2.216

In version 2.216 of the font, bottom anchors for several letters with descenders have been moved to more standard locations. Contextual kerning has been added for double diacritics so that they clear combining marks on neighboring glyphs. See the Junicode Manual § 4.12, for details.

Junicode version 2.215

The Junicode font is primarily for scholars and students of the Middle Ages, but it serves users with a wide variety of interests. It tracks the development of the Medieval Unicode Font Initiative (MUFI), with its wealth of specialized medieval characters, but it also provides many OpenType features that allow users to access MUFI characters in accessible ways.

Junicode is an extended font family, with five weights and five widths. This makes for a large number of font files, but the font also comes in a variable version, in which all the capabilities of the traditional “static” version—and more!—are packaged in just two files. The variable version is especially suitable for web use, but variable fonts can also be used in Adobe InDesign, Affinity Publisher, LibreOffice, LuaTeX, and other text-processing apps (see the file JunicodeManual.pdf for details).

Version 2.215 fixes some problems with anchors on the letter i and supplies some modifier letters (with ogonek, accessible via sups) for linguistic uses.

The static .ttf version of Junicode is now unhinted because of problems with the autohinter. The .ttf fonts will still work well on the Mac and most Linux systems, but Windows users should prefer the .otf version. The variable version is .ttf, but it is manually hinted rather than autohinted: it should work well in all apps that can use variable fonts.

Junicode version 2.214

The Junicode font is primarily for scholars and students of the Middle Ages, but it serves users with a wide variety of interests. It tracks the development of the Medieval Unicode Font Initiative (MUFI), with its wealth of specialized medieval characters, but it also provides many OpenType features that allow users to access MUFI characters in accessible ways.

Junicode is an extended font family, with five weights and five widths. This makes for a large number of font files, but the font also comes in a variable version, in which all the capabilities of the traditional “static” version—and more!—are packaged in just two files. The variable version is especially suitable for web use, but variable fonts can also be used in Adobe InDesign, Affinity Publisher, LibreOffice, LuaTeX, and other text-processing apps (see the file JunicodeManual.pdf for details).

Version 2.214 includes improved superscript and subscript shapes, sizes, and anchors; it also fixes kerning for French sequences consisting of L + apostrophe + word-initial h or vowel.

Junicode version 2.213

The Junicode font is primarily for scholars and students of the Middle Ages, but it serves users with a wide variety of interests. It tracks the development of the Medieval Unicode Font Initiative (MUFI), with its wealth of specialized medieval characters, but it also provides many OpenType features that allow users to access MUFI characters in accessible ways.

Junicode is an extended font family, with five weights and five widths. This makes for a large number of font files, but the font also comes in a variable version, in which all the capabilities of the traditional “static” version—and more!—are packaged in just two files. The variable version is especially suitable for web use, but variable fonts can also be used in Adobe InDesign, Affinity Publisher, LibreOffice, LuaTeX, and other text-processing apps (see the file JunicodeManual.pdf for details).

Version 2.213 (2.212 was a special version, not released) addresses several issues raised since Dec. 2024, including: superfluous diacritics appearing over some Greek letters; added Latin subscript letters defined in Unicode; added "bottom" anchors to basic Latin modifier letters.

Junicode version 2.211

The Junicode font is primarily for scholars and students of the Middle Ages, but it serves users with a wide variety of interests. It tracks the development of the Medieval Unicode Font Initiative (MUFI), with its wealth of specialized medieval characters, but it also provides many OpenType features that allow users to access MUFI characters in accessible ways.

Junicode is an extended font family, with five weights and five widths. This makes for a large number of font files, but the font also comes in a variable version, in which all the capabilities of the traditional “static” version—and more!—are packaged in just two files. The variable version is especially suitable for web use, but variable fonts can also be used in Adobe InDesign, Affinity Publisher, LibreOffice, LuaTeX, and other text-processing apps (see the file JunicodeManual.pdf for details).

Version 2.211 includes various new glyphs along with minor improvements and fixes. The TeX package include a couple of bug fixes; and one can now select a fontspec/LuaTeX renderer via the renderer package option.

This release continues to offer a static TTF version along with variable TTF and OTF versions. Users of the static font should choose the OTF version unless there is a specific reason for choosing the TTF.