Laurent Pugin
Laurent Pugin
Thank you for the proposal. I agree that reading and maintaining the functor codes is not great as it is because it is spread in multiple files. Here are a...
@craigsapp I am going to merge this. I double checked the changes in `iohumdrum.cpp` and it should be fine.
I agree it would be nice to have this and I like the proposal to support this with `pgHead` and `pgFoot` with `@position` rather than adding specific elements. It seems...
I would suggest `@position` = `first | second | last | even | odd` ? * `first` would correspond to the current `pgHead` / `pgFoot` * `second` would correspond to...
> OK. How will duplicate values of ***@***.***’ be handled? Assuming such things will be illegal, what mechanism will disallow/handle the following – ```xml … … ``` > ? I...
The example did not make it through. You can paste it here if it is now too long. I believe that, if Schematron can constrain what we want, then we...
> A variation of this is to use pgHead and pgFoot elements with position values of “first | last | alt1 | alt2”. I think I like this more, but...
It does make sense. I think that for backward compatibility we need a replacement for what `pgHead2` currently does. That is, defining a header from the second page onwards, but...
I would actually now leave it as it is. In terms of backward compatibility, if someone has data where only `` is encoded - which as I understand is the...
Excatly, this is the idea. Works for you?