pe-ro

I agree that `@func` isn't appropriate here. But I'm also not particularly fond of `@scope` either. `@scope` sounds too broad, as though one can describe a range of possibilities when...

`tempo/@func` has a very specific purpose -- to provide a clue to the purpose of the marking. That is, it allows only the following values: ``` Marks a gradual change...

I'd like to roll back the conversation just a bit, when @craigsapp said: >The basic algorithm for `` when condensing would be to place the staff 1 text on staff...

Like @craigsapp says, I can't foresee the consequences of relying on `@part` to indicate how `` is to be displayed when condensing/expanding a score. Hence the need for a new...

@lpugin, using Boolean values for `@system` doesn't allow one to capture where the directive is placed relative to the system like "above" and "below" do.

@ahankinson said > What about something where you can say that a `` is attached to all staves, rather than one single staff? That would avoid the use of the...

The `` element is provided for those cases where a key signature needs to be "elevated" to element status, usually in order to attach new/extra attributes, for instance to capture...

@odub: As you've discovered, the encoding tools have not been maintained as rigorously as they should be. None of them come with a guarantee of fitness. 😃

To verify that removing the version check actually works, you should validate your output against the latest schema.

I wouldn't say that the `` example is wrong, but that perhaps the "Substitutions, Restorations, and Handshifts" part of the Guidelines is incomplete. Without the use of `` to gather...