SMuFL 1.12 and Bravura 1.12 released

We are pleased to announce the release of SMuFL 1.12, the first update to the specification since the release of SMuFL 1.0 in June of last year. This is a minor update, and as promised does not change any of the code points or canonical names of any of the existing glyphs.

A small number of new glyphs has been added, including two new ranges to extend the repertoire of glyphs in existing ranges that have been filled up, which have been named Time signatures supplement and Octaves supplement (following the conventions used by the Unicode Consortium for such situations).

Two new types of metadata for the glyphsWithAnchors structure have also been added: noteheadOrigin, intended to help with the correct alignment of noteheads of different widths with each other (in particular, the double whole (breve) notehead with two vertical lines to either side of its oval notehead); and opticalCenter, intended to help with the correct alignment of glyphs with noteheads and stems (in particular, glyphs in the Dynamics range). Full details of these new points, including illustrations, are included in the Notes for implementers section of the updated SMuFL specification.

For full details of the changes to glyphs, ranges, and metadata in SMuFL 1.12, consult the version history, or download the updated SMuFL 1.12 specification.

The Bravura font family has also been updated to version 1.12, implementing the new glyphs and metadata specified in SMuFL 1.12. Bravura has in fact been updated several times independently of SMuFL since the release of SMuFL 1.0 in June last year, to fix a few minor bugs, and to improve the design of specific glyphs. In particular, I would like to extend my thanks to Tucker Meyers, who has produced improved versions of the G, F, and C clefs (and their variants), the octave markers, and the digits used for tuplets, which were added in Bravura 1.08 in November last year.

Full details of the changes in Bravura and Bravura Text can be found in the FONTLOG file included in the redistributable package, which contains OTF, EOT, WOFF, and SVG versions of both fonts, together with the font-specific JSON metadata.

Development of SMuFL will continue, as dictated by the needs of its community, and I encourage you to get involved in the ongoing discussion. If you are using SMuFL or Bravura for your project, I’d love to hear about it, so please get in touch to let me know what you’re working on.

Leave a Reply