Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify intended metrics guidelines for three ranges #178

Closed
mdgood opened this issue Feb 18, 2021 · 1 comment
Closed

Clarify intended metrics guidelines for three ranges #178

mdgood opened this issue Feb 18, 2021 · 1 comment
Assignees
Milestone

Comments

@mdgood
Copy link

mdgood commented Feb 18, 2021

The SMuFL spec talks about having two fonts, one for scoring applications and one for text-based applications. There are different metrics and glyph registration guidelines for scoring applications and text-based applications.

However there are three ranges - Beamed groups of notes, Metronome marks, and Standard accidentals for chord symbols - where the intent is to mix musical symbols with text. It seems this intent applies equally to scoring applications and text-based applications.

It would seem that these three ranges should use the text metrics and glyph registration guidelines rather than the scoring metrics and glyph registration guidelines. However this is not clear from the implementation notes for these ranges, each of which starts:

This range is most useful in fonts intended for text-based applications, with metrics that are compatible for mixing musical symbols with text.

If it is correct that the text-based metrics and glyph registration guidelines should be used for these ranges, even in a font designed for scoring applications, could we please state that clearly? The current writing is confusing on this point.

Perhaps the first sentence in the implementation notes for each range could be replaced with something like:

This range is intended for mixing musical symbols with text. Its metrics and glyph registrations should follow the guidelines for text-based applications, even in a font intended for scoring applications.

I know this is late in the game for SMuFL 1.4, but I've recently found that this has confused several spec readers. Since it's a small targeted change in three areas, and it seems to match current practice with SMuFL fonts, hopefully it could still make it in. That is assuming of course that this interpretation of the intent for these ranges is correct and the wording change is not controversial.

@dspreadbury dspreadbury self-assigned this Mar 2, 2021
@dspreadbury dspreadbury added this to the SMuFL 1.4 milestone Mar 2, 2021
@dspreadbury
Copy link
Contributor

This does seem like a reasonable request. I will take a look at squeezing this in to SMuFL 1.4.

dspreadbury pushed a commit that referenced this issue Mar 15, 2021
…of notes', 'Metronome marks' and 'Standard accidentals for chord symbols' ranges that their glyphs should follow the guidelines for text-based applications even in fonts that are primarily intended for use in scoring applications. This fixes #178.
dspreadbury pushed a commit that referenced this issue Mar 15, 2021
…-pick the changes for #178 and #179 and apply them to the draft dated 2021-02-14 to avoid having to publish a whole new draft for those changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants