You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For me, an arpeggiato is a vertical wiggle (similar to the horizontal trill wiggle) to the left of a chord. Glissando wiggles have an arbitrary angle.
So I think the Arpeggiato glyphs (U+EAA9 -> U+EAAE) should be rotated by 90 degrees in https://w3c.github.io/smufl/gitbook/tables/multi-segment-lines.html
In particular, EAAD should point upwards and EAAE should point downwards.
The text was updated successfully, but these errors were encountered:
No, due to the way in which fonts for nominally left-to-right writing systems are rendered by all current font technologies, it is more practical to have these glyphs drawn horizontally so that a longer wiggle can be created simply by drawing a run of the same glyphs over and over again, and then have that drawn string rotated at draw time.
Okay, but to avoid any confusion, I think the Implementation Notes should include examples of both glissando and arpeggiato construction using the defined glyphs.
(I used vertically oriented wiggles in Stockhausen scores. They were used in text strings containing carriage returns. The strings were subject to the usual graphic and text transformations...)
For me, an arpeggiato is a vertical wiggle (similar to the horizontal trill wiggle) to the left of a chord. Glissando wiggles have an arbitrary angle.
So I think the Arpeggiato glyphs (U+EAA9 -> U+EAAE) should be rotated by 90 degrees in
https://w3c.github.io/smufl/gitbook/tables/multi-segment-lines.html
In particular, EAAD should point upwards and EAAE should point downwards.
The text was updated successfully, but these errors were encountered: