Daniel Spreadbury

It's certainly true that the noteheads in the [Note name noteheads](https://w3c.github.io/smufl/gitbook/tables/note-name-noteheads.html) range are currently oversized by around 8%. I'll look at adding a stylistic set for these oversized versions and...

Further feedback from @fkretlow on the revised figures and accidentals in Bravura 1.37: > I think both numbers and accidentals look good, you have found a good balance between readability...

Thanks for reporting this, Werner. You're right that this is incorrect. We'll either fix this so that it correctly assigns codepoints in the next PUA range, or consider preventing it...

We don't have any formal way of packaging Bravura at the moment. In principle I'm open to setting something up, or to provide assistance to whoever would want to set...

Thanks for reporting this. I'll make sure it is fixed in the next Bravura release.

Perhaps we could consider setting up a project on Transifex for this, if SMuFL qualifies as a sufficiently open source project for their "forever free" plan.

I've spent a bit of time this morning speculatively setting up a Transifex project for localising the glyph names and range names metadata: www.transifex.com/w3c-music-notation-community-group/smufl/ I've simply uploaded the current **glyphnames.json**...

At the suggestion of @adrianholovaty, I've also imported the **glyphnames.json** and **ranges.json** data into POEditor, another translation platform that he personally uses for Soundslice. It would be interesting to know...

Apologies, @Jojo-Schmitz, I don't seem to have had a notification from Transifex of your request, but I've now approved you to join the team.

If you let me know your Transifex username, I can invite you to the German team, Klaus.