kepper
kepper
At today's ODD Friday, we were much in favor of @KristinaRichts' last proposal, in conjunction with @ahankinson's additions. It seems important to have solid documentation on this, so we hope...
I'm afraid I haven't had the time to work on this one and prepare something together with the Metadata IG. I propose to push it one more month, assuming that...
Many thanks to @doerners and @musicEnfanthen for the great work on this. Now it seems time to get back to the Metadata IG and revise how your proposal aligns with...
might be a candidate for promoting information to elements, but this requires more careful inspection
yes, we should. However, I just noticed that some examples use `@fontname`, namely [`tempo-01.mei`](https://github.com/music-encoding/guidelines/blob/master/mei/dev/tempo-01.mei) (and there might be others…).
during 2022 dev meeting in Berlin, @fujinaga, @lpugin, @pe-ro, @musicEnfanthen and @kepper came to the conclusion that we keep it as it is, to allow fallbacks and some such. Closing...
This whole discussion reminds me about the argument I've given [elsewhere](https://github.com/music-encoding/music-encoding/pull/846#issuecomment-889022967): Sometimes, music notation simply doesn't want to follow our criteria for what is a control event and what is...
The current proposal doesn't easily support connecting layers 1 and 3 plus 2 and 4 of four instruments spread across two staves. However, we didn't do that in the past,...
But that is a separate discussion, isn't it? What I would propose is to have two flavors of `att.common`, which can be referenced as needed. Regular `att.common` would bring `att.nNumberLike`...