Re: SMuFL Metadata for ligatures and alternates

Hi Jonathan,

Because ligatures and stylistic alternates are not part of the core set of 
SMuFL characters, the SMuFL metadata files can't provide any details about 
where these things might be found in specific fonts. However, the Bravura 
JSON metadata file does contain details of all of the optional glyphs and 
ligatures, in the glyphsWithAlternates, ligatures, optionalGlyphs, and 
sets nodes of the metadata file.

https://github.com/steinbergmedia/bravura/blob/master/redist/bravura_metadata.json


For the alternates, you can get a description by getting the description 
for the core glyph for which this is an alternate, though you can't easily 
come up with a human readable description; you could come up with one by 
matching the alternate glyph name with the core glyph name, and taking the 
remaining substring and adding it to the end of the core glyph's 
description in parentheses, perhaps.

For the ligatures, you could do a similar thing: get the human-readable 
description for the core glyphs that are listed in the ligature and append 
them together with some kind of separator to make a description.

Daniel



From:   Jonathan Greenberg <jgreenberg@rilm.org>
To:     public-music-notation-contrib@w3.org
Date:   22/07/2016 16:16
Subject:        SMuFL Metadata for ligatures and alternates



​​
We an using BravuraText in a web-based XML editor for MGG Online (a 
German-language music encyclopedia), and most of the use cases for 
inserting SMuFL character are one character at a time. (As an example, for 
the article on "Furlana": " Seit dem 16. Jh. wurden aber bereits 
Musikstücke mit dem Titel ballo furlano im einfachen zweizeitigen Takt 
(&#xE08B; oder 2/2) und mit bewegtem Tempo gedruckt.")

Because of this, and because we have not built an application to allow 
users to position glyphs relative to one another, our authors and editors 
cannot insert strings of SMuFL characters into their text. In order to 
make this work, we need to offer the recommended ligatures in addition to 
the standard set of of SMuFL code points. The problem is that, while 
ligatures and alternates are includes in the SMuFL documentation, the 
SMuFL metadata files (which we use to created configuration files for our 
XML editor) do not contain ligatures or alternates. Would it be possible 
to provide a second set of metadata files that include the ligatures and 
alternates? Right now, we're using the metadata file for BravuraText to 
generate metadata for ligatures and alternates, but that files doesn't 
contain a "Description".

Many thanks,
Jonathan


Jonathan Greenberg, Product Development Coordinator
RILM International Center
365 Fifth Avenue, Suite 3108  •  New York, NY 10016-4309
Phone 1 212 817- 8611 •  www.rilm.org

***New*** RILM music encyclopedias
An entire music library’s bookcase is just one click away.
www.rilm.org/encyclopedias





- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Steinberg Media Technologies GmbH, Frankenstrasse 18b, D-20097 Hamburg, Germany
Phone: +49 (40) 21035-0 | Fax: +49 (40) 21035-300 | www.steinberg.net
President: Andreas Stelling | Managing Director: Thomas Schöpe, Hirofumi Osawa
Registration Court: Hamburg HRB 86534
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -