From: Daniel Spreadbury
Thanks for the explanation. It all make sense now :-) It leaves me with
a question though.
I am creating (well enhancing) text fonts designed to be usable in the
simplest of circumstances: eg Windows NotePad, simple static controls on
old fashioned dialogue boxes, and so on, in which
- OTF ligatures may or may not be respected
- changing fonts may not be possible
- using subscripts and superscripts may not be possible.
[For chord names I am therefore restricting myself to writing them along a
line - like G#7b5 (rather than fancier styles with superscripts above
subscripts).]
So
[Diminished/Half-diminished]
> They're on the baseline because there are multiple conventions for their
alignment in chord symbols...<
I can see that leaving them on the baseline provides a well defined starting
point for operations like creating superscripts. But if I put them at the
SMuFL code points in my simple text fonts, then, for the above reasons,
they'd have to be raised and small like the ASCII degree symbol. So while
they'd conform to SMuFL code points, they wouldn't conform to the expected
metrics.
The same goes for the accidentals: I see that in Bravura text, the
accidentals from U+E260 are positioned (I think) on the middle line of a
5-line staff of the caps height. Mine would be positioned to appear lower.
Can I assume that (for the simple purposes for which my fonts are designed)
this would not be a problem?
Dave
David Webber
Mozart Music Software
http://www.mozart.co.uk/#############################################################
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]>
Locked
