w3c/smufl

timeSigCombNumerator doesn't work as expected, it is placing number in the denominator position

drscottlobo opened this issue · 2 comments

drscottlobo commented

Hi there! I love Bravura text and really appreciate all the awesome work that has been put into the SMUFL spec! I'm currently using Bravura Text in a webpage to display time signatures. I'm using a template string like this to render a 2/4 time signature in a react app like this:

<span fontFamily="BravuraText">{`\uE09E\uE082\uE09F\uE084`}</span>

I'm following the spec's instructions for combining time signature numerator and denominator: "uniE09E_uniE082_uniE09F_uniE084" per the SMUFL specification on this page: https://w3c.github.io/smufl/latest/tables/time-signatures.html?highlight=time%20sig#time-signatures-ue080ue09f

The issue is that the TimeSigCombNumerator isn't functioning as expected, instead it is placing both numbers in the denominator place, which means I end up with the 2/4 overlapping each other in the denominator place. Is it possible the TimeSigCombNumerator just has a bug that is placing the text in the wrong vertical space?

Thanks for any help!

dspreadbury commented

I just tried this myself in TextEdit on my Mac, and the 4/4 time signature appears as expected. I'm not sure about how to do this in a React app, but so far as I can see, the ligature is working correctly.

drscottlobo commented