Emil wrote:
> I would suggest that if some characters are clearly ligatures, it should
> be recommended that they are to be defined as OpenType ligatures,
> despite assigning them codepoints. Dynamic letters are the example.
This is indeed what I have already outlined: give a glyph a name that
shows it's a ligature (e.g. for "mp" a name of "uniE561_uniE560"), define
it in the liga table, and assign it a codepoint in the agreed-upon range,
> If SMuFL aims to be a superset of Unicode Musical Symbols range,
> then some of ornaments should be obligatory defined as ligatures
> of the ornament strokes, as they are currently encoded in Unicode.
I don't think that's correct. Although there are 11 combining glyphs
included in the Unicode Musical Symbols range for creating ornaments,
there are no actual ornaments that use these combining glyphs defined in
the range.
Daniel
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Steinberg Media Technologies GmbH, Frankenstrasse 18b, D-20097 Hamburg, Germany
Phone: +49 (40) 21035-0 | Fax: +49 (40) 21035-300 | www.steinberg.net
Managing Director: Andreas Stelling, Kazunori Kobayashi
Registration Court: Hamburg HRB 86534
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#############################################################
This message is sent to you because you are subscribed to
the mailing list <
[hidden email]>.
To unsubscribe, E-mail to: <
[hidden email]>
To switch to the DIGEST mode, E-mail to <
[hidden email]>
To switch to the INDEX mode, E-mail to <
[hidden email]>
Send administrative queries to <
[hidden email]>