- From: Michael Good <mgood@makemusic.com>
- Date: Tue, 5 Dec 2017 10:34:37 -0800
- To: Michael Scott Cuthbert <cuthbert@mit.edu>
- Cc: "public-music-notation-contrib@w3.org" <public-music-notation-contrib@w3.org>
- Message-Id: <F21E4AEB-A664-4E06-8CFB-8FF40490D9E8@makemusic.com>
Hi Myke, The SMuFL attributes and the tags that use SMuFL names as content use SMuFL canonical glyph names. So if there is a canonical glyph name for a ligature, that could be used. However this would not work for things like creating a specific trill or mordent from the "Combining strokes for trills and mordents” range. These would require using higher-level MusicXML features, combining symbols in standard MusicXML ways, or using the various other- elements and extension features. Best regards, Michael Good VP of MusicXML Technologies MakeMusic, Inc. > On Dec 5, 2017, at 10:10 AM, Michael Scott Cuthbert <cuthbert@mit.edu> wrote: > > One question that I’m still not clear of the answer to in MusicXML 3.1 — in the smufl tags, will it be possible to create composite characters? Quite a number of important ones (esp. for early music) are designed to be created with multi-character ligatures. But it seems like most of the new smufl support is for replacing a symbol with a single character. > > Best, > Myke > > > >> On Dec 5, 2017, at 13:03, Michael Good via GitHub <sysbot+gh@w3.org> wrote: >> >> >> The following commits were just pushed by mdgood to https://github.com/w3c/musicxml: >> >> * Update date to reflect latest XSLT change >> by Michael Good >> https://github.com/w3c/musicxml/commit/4b7f4a97abe90703be2115b355ad3841bf670c75 >> >> * Merge pull request #247 from w3c/report >> >> Update date to reflect latest XSLT change >> by Michael Good >> https://github.com/w3c/musicxml/commit/9150d4be2d02548be01f9f1cb40d89840b442747 >> >> >
Received on Tuesday, 5 December 2017 18:35:04 UTC