musescorefonts / leland Goto Github PK

The SMuFL specification changed on code point U+EAAE:
https://www.smufl.org/version/latest/range/multiSegmentLines/
https://w3c.github.io/smufl/latest/tables/multi-segment-lines.html

see fkretlow/sebastian#4
This will probably have to be touched in MuseScore too.

Will this (or does this already) provide characters for the unicode music notation block (1D100..1D1FF, cf. https://unicode.org/charts/PDF/U1D100.pdf), in addition to the private use area definitions?

The slash glyphs in the tremolo range (U+E220 – U+E229) are supposed to be centered on the glyph origin, but instead are left-aligned to the origin.

See: https://w3c.github.io/smufl/latest/tables/tremolos.html

Noticed this issue in Dorico Version 5.0.20.2042 (Jul 5 2023). The dynamics separator are not appearing.

Bravura:

Leland:

https://github.com/w3c/smufl/releases/tag/v1.4 states:

SMuFL 1.4 is the second release of SMuFL prepared by the W3C Music Notation Community Group.

This release adds more than 150 new glyphs in existing and new ranges. Brand new ranges added in this release include 'Chop (percussive bowing) notation', 'Techniques noteheads' and 'Scale degrees', and supplemental ranges have been added for 'Extended Helmholtz-Ellis (just intonation) accidentals', 'Other accidentals', 'Medieval and Renaissance prolations', 'Noteheads', 'Note name noteheads'. SMuFL 1.4 also expands the capabilities of font-specific metadata files, including the ability to specify the design size for a font, specify complementary a text font to be paired with the font, and some additional line widths.

The specification can be found at https://w3c.github.io/smufl/releases/1.4/. I think the font-related metadata is one of the low hanging fruits Leland can add immediately, specifically "textfontName": ["Edwin", "serif"].

The breve rest in the Leland font is very wide:

Compare to Bravura:

See: https://www.smufl.org/version/latest/range/rests
Also the Wikipedia entry about rests: https://en.wikipedia.org/wiki/Rest_(music)
where such a wide rest is not presented or discussed.

The source of the problem is that this is SCORE's breve rest, but if this is not a mistake in SCORE, then it is a very minority style for breve rests that I have not seen elsewhere.

Breve rests are rare in modern scores, but more common in older scores. Here is an example use in a full score:

Leland font version:
https://verovio.humdrum.org/?file=jrp:Jos2707&k=ey&font=leland

Bravura font version:
https://verovio.humdrum.org/?file=jrp:Jos2707&k=ey&font=bravura

The rest is too prominent compared to the notes. It also roughly has the same shape as a notehead which can decrease readability. In mensural music (which the above examples are a minimimally adapted from), that shape is actually a note: In white mensural notation (used predominantly from 1450-1600) it is a colored breve (usually meaning a triplet breve), and in black notation (used predominantly from 1300-1450) it is a normal breve note. So the Leland font cannot be used for mensural music unless this rest is fixed to the more standard thinner shape.

See https://www.smufl.org/version/latest/range/medievalAndRenaissanceIndividualNotes
And in particular U+E952 "Black mensural brevis"

Hey there, this might be just my screen but I get the feeling there is some kind of small bump on each of the full notes. The top also doesn't seem perfectly smooth, but it's less pronounced.

The vertical lines of the double whole noteheads do not match the default stem thickness in the engravingDefaults.

I'm not sure if the stem thickness value in the metadata should be adjusted or the glyph.
Currently the "stemThickness" is set to 0.11 but should be more like 0.145 (although MuseScore only supports two decimals).

Refers to #19

Noticed an issue with down arpeggio arrows in Dorico which doesn't seem to be present in MuseScore.

Would it be possible to get the narrow, serif time signatures which correspond to Leland when selecting the option to use larger time signatures above staves? [Currently using Dorico 4.3. When switching to other fonts, the time signature font changes automatically.] Thank you!

It would be good to have the complete Bar repeats range available, for repeat-beat abbreviations:

(Behind Bars, p. 230)

Release claims it has

Added missing points at extrema throughout

Still the following have missing points:

• E054
• E07A
• E083
• E087
• E240
• E285
• E517
• E518
• E519
• E51E
• E562
• E563
• E650
• E651

Can you please clarify this installation issue for use with Dorico (Mac)? (Apologies in advance for being a GitHub novice, and musician rather than techie!)

Your advice is:
To use the font in Dorico (1.0.20 and later), the metadata.json file needs to be copied to the following location:
Mac: /Library/Application Support/SMuFL/Fonts/leland/leland.json

When I try to download <metadata.json> it downloads as an html file. If I put this in a folder created as /Library/Application Support/SMuFL/Fonts/leland/leland.json , Dorico refuses to load, as it tells me that metadata.json is in the incorrect format. Do I need to find a way to download it as other than html, or rename it, or something else, please?

I have no experience using music fonts but I notice that the character for stem(U+E210) is seemed missing from the leland font, is it true?

Just noticed that diamond noteheads intersect stems in grace notes, in this case harmonics, and was wondering if this is intended behaviour. Two different results in Dorico and MuseScore.

Dorico:

Musescore:

I realize that this is probably the smallest possible gripe, but when you zoom into notes, you'll notice a small misalignment between the head and stem of the note.

As you can see, it's really small, but it would be great to fix this if easy.

https://SemVer.org

Okay, okay, I get it... it wasn't designed for Finale. Nevertheless, that is the software I've got for now, the one I know best, my primary tool. As of version 27 (and, presumably, any version after that), it's supposed to support SMuFL fonts. Naturally, I decided to try Leland, assuming that installing the font, putting the JSON file in the appropriate folder for metadata, and renaming it, would do the trick.

We must all have our pleasant fantasies. Attempting to switch the default music font to Leland in Finale's new SMuFL-ready template produces an error window about Finale not supporting changing the font from SMuFL to non-SMuFL. Odd... this is supposed to be SMuFL-compliant, what's the deal?

Alright, fine, says I... I'll load up a non-SMuFL legacy template and try to change it there since Finale is not reading it as SMuFL somehow. The result is attached; namely, much like in days of yore when one tried to use a SMuFL font in Finale, it produces gibberish. Any advice? Is this likely to ever be fixed, or is Finale pretty much being abandoned as NOFP? (i.e. Not Our F****** Problem)

At this point an unsuspecting user might assume that the font will work in Sibelius/Finale if they just install the otf. It might be worth mentioning that the font is not yet compatible with these software packets.

The glyph U+E0A5 noteheadNull is expected to have a width that matches those of the other noteheads, but in Leland currently it has no width at all.

When using harp pedalling indications in Dorico, the accidentals were still those of Bravura.
I posted on the Dorico group to first check whether this is a Dorico or Leland problem, and upon investigation by one the users, changing the Music Text Character Style to Leland Text, the accidental appeared as follows.

According to the user, "It seems the required characters are the standard Unicode text glyphs for accidentals (U+266D, 266E and 266F), not the SMuFL ones (E260, E261, E262) – which Leland Text lacks." Would it be possible to implement this?

Original post on the Dorico forum, with the solution posted in the replies: https://forums.steinberg.net/t/harp-pedaling-accidentals-font/848220/5

Please add the "filled" versions of the heads for whole notes and half notes (U+E0FA + U+E0FB).

FontForge complains about "missing points at extrema" for the following glyphs

• E083
• E087
• E0A2
• E1D2
• E22E
• E22F
• E230
• E231
• E240
• E285
• E4A2
• E4A3
• E4AE
• E4AF
• E4B0
• E4B1
• E4B2
• E4B3
• E562
• E563
• E566
• E5C7
• E650
• E651
• E653
• ED24

To prevent:

Thank you so much for this new font, this is such a great effort. I am interested in using Leland with LilyPond, since it is SMuFL compliant. I just wanted to ask whether Leland support different types of flags (since, as far as I know, MuseScore itself doesn't). LilyPond supports multiple types of flags for a same font, e.g.:

The second style above, flat flags, is particularly interesting for me as it is quite commonly used in the contemporary music repertoire I work with. The angled straight flags are also fairly common in the modernist repertoire of the mid-20th century (e.g. most Boulez music engraved by Universal Editions). Does Leland support those by any chance?

It would be nice if you could add a restQuarterZ glyph.

Currently the standard double whole note only has one vertical line on each side instead of two. According to SMuFL specs this should rather be an alternate glyph: https://www.w3.org/2019/03/smufl13/tables/noteheads.html#recommended-stylistic-alternates

The breve head (noteheadDoubleWholeSquare) looks disproportionately wide. It is too thin compared to the normal whole notehead. And in most classic prints I looked up the vertical lines spread almost two staff spaces. Here are some examples:

There are several glyphs that have problems. Some show a wrong drawing direction, that may lead to problems in one applications when they collide. Others are self intersecting, which will not render correctly because they do not have a “inside” and “outside”.
Here's a list:

Wrong Direction

• E001
• E004
• E1D9
• E26D
• E281
• E4A1
• E4A3
• E4A5
• E4A7
• E4B1
• E4B3
• E4B5
• E4B7
• E4B9
• E4BB
• E4C1
• E4C5
• E4C9
• E4F2
• E4F5
• E568
• E611
• E613
• E630
• EAAA

Self intersecting

• E04B
• E1DA
• E1DB
• E1DC
• E242
• E4ED
• ECA9
• E5DF

Noticed this issue on Dorico Version 5.0.20.2042 (Jul 5 2023). The fast to slow graphic on trill lines does not adapt accordingly.

Bravura:

Leland:

1 serious error was found. Do not use this font file.

I'm sure it's some annoying Apple requirement that's an easy fix.

Oops

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 glyphBBoxes field of the SMuFL metadata has a bounding box for a glyph named sustainedBuzzRoll which doesn't seem to be described anywhere.

I can't find this glyph name in the SMuFL list of glyphs.

Did you maybe forget to describe it in the optionalGlyph field of the metadata ?