Benjamin W. Bohl

> > @ahankinson transferred this issue from music-encoding/music-encoding on Apr 12 > > Should discussions about new features (or changes in features) be placed here (music-encoding/guidelines) or in (music-encoding/music-encoding)? I...

@craigsapp is this solved with https://github.com/music-encoding/music-encoding/pull/853?

@dspreadbury I'm delighted to see this has been added to the [SMuFL 1.5](https://github.com/w3c/smufl/milestone/4) milestone! There is yet another variant of the three-quarter sharp to be added from Zimmermann’s autographs: a...

@dspreadbury I fixed some naming inconsistencies in the pull request and I could also provide characters for the Bravura font, what would be the best way for doing that?

checked the above errors and marked those that I could load

@musicEnfanthen, an "archive" or "stale" tag or section sounds like a good idea. If we remove them, someone might stumble over them on the web and want to re-add them...

I like the idea of dividing the different possibilities into different values!

> I'm a little unsure about the value "steppedMelodicContour". Can we replace it with "numericMelodicContour"? I think this term is a better match with "diatonicMelodicContour". Also, it might be worth...

I gave this some more thought: I think the name should express the content. This is perfectly true for **parsons**, because it’s known enough to be considered a terminus technicus....

Welcome, @paxbun and many thanks for your question, which is, of course, very welcome! As @rettinghaus pointed out, the textual content of `octave` can indicate this, although this is just...