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
I’m experiencing a misalignment issue when trying to create certain time signatures using SMuFL glyphs.
Example 1: 12/8 Time Signature
When rendering the 12/8 time signature, it displays correctly:
HTML code for 12/8:

Example 2: 10/8 Time Signature
However, when I change the time signature to 10/8, it becomes misaligned:
HTML code for 10/8:

Issue Summary:
The alignment works fine for some time signatures (e.g., 12/8, 4/4), but for others like 10/8, 2/8, 8/8, and many others, the numbers do not align vertically.
This issue causes inconsistent alignment across various displays.
Questions:
Is there a recommended solution or workaround to ensure consistent vertical alignment of SMuFL time signature glyphs?
Are there any known issues with specific glyphs or font metrics that might be causing this problem?
The text was updated successfully, but these errors were encountered:
Bravura's behaviour in this regard is based on ligature substitution, where typing in the individual characters in succession substitutes them with a separate ligature glyph representing the complete signature. Bravura does not have a ligature for 10/8, or any other multi-digit numerator signature except for 12/8, and so will not be able to display them correctly.
The best and only real solution, as far as I know, is to use/develop a font which supports the ligatures you need.
Misalignment Issue with SMuFL Time Signatures
I’m experiencing a misalignment issue when trying to create certain time signatures using SMuFL glyphs.
Example 1: 12/8 Time Signature
When rendering the 12/8 time signature, it displays correctly:
HTML code for 12/8:
Example 2: 10/8 Time Signature
However, when I change the time signature to 10/8, it becomes misaligned:
HTML code for 10/8:
Issue Summary:
Questions:
The text was updated successfully, but these errors were encountered: