Laurent Pugin

1. I think we would need something similar to https://github.com/rism-digital/verovio/blob/develop/fonts/supported.xsl to list the alternates we support. With this in hand, alternate codepoints glyphs will be extracted as well as their...

Related to https://github.com/rism-digital/verovio/issues/800 See the current MEI guidelines https://music-encoding.org/guidelines/dev/data-types/data.METERFORM.html

I am not sure this is `a complex metrical pattern` and it looks over the top to me. Everything fits within a `` and it seems to be simply a...

It can be both, CWMN and mensural. You can see some CWMN examples here https://github.com/music-encoding/music-encoding/issues/504#issuecomment-387035283

In my opinion they do look like control events. So maybe another idea would be to have `damp` to qualify a `` as suggested here https://github.com/music-encoding/music-encoding/issues/712 ?

I don't. I prefer to separate them and leave `@type` totally free for project specific uses.

My point is that if we start (again) to fill `@type` with pre-defined values, then `@type` is not completely free for project specific needs. In other words, documenting its use...

> The origin point for the top-page-margin options has changed recently I suspect this PR https://github.com/rism-ch/verovio/pull/1523/files but I am not absolutely sure

Should be addressed by https://github.com/rism-digital/verovio/pull/2632

(The MEI posted in #1481 does not contain any `mRest`.) The result of the MusicXML conversion of the example above leaves me doubtful:  ```xml heav en, what a ```...