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
When trying to use Leland on a web page, there is nothing for many SMuFL code points. Especially Chord symbols (U+E870–U+E87F). Is this font expected to be usable on web pages? For the notation I did find, the characters would not align with other text. It is mostly too large at the same font size.
The text was updated successfully, but these errors were encountered:
There's no reason why the font couldn't be used on a web page, but the character set is indeed very incomplete at the moment. We prioritised the most essential notation elements for this first version, based on what we needed for MuseScore. In MuseScore, Bravura is used as a fallback for any missing characters (since it's the 'reference font' for SMuFL), but when using Leland elsewhere one can't rely on similar functionality.
If you want to use music characters alongside normal text, then Leland Text (as opposed to Leland) is explicitly meant for that purpose, and its symbols should be more appropriately sized for that purpose (i.e. smaller than those in Leland). But for now the character set of Leland Text is even more limited, again, mostly including only what is necessary for use in MuseScore - essentially, accidentals, dynamics, and metronome marks.
Naturally, the plan is to expand the character set over time, so it would be useful to know exactly the context in which you're trying to use the font, so we know what to prioritise working on next. (I suspect that chord symbol characters might be a popular request) :)
When trying to use Leland on a web page, there is nothing for many SMuFL code points. Especially Chord symbols (U+E870–U+E87F). Is this font expected to be usable on web pages? For the notation I did find, the characters would not align with other text. It is mostly too large at the same font size.
The text was updated successfully, but these errors were encountered: