I suppose it really depends on what the headers should be for.
If they are simply to store metadata, then there is no need to raise an
error and even a warning may be a bit much in some situations.
If, however, the headers are to be considered active directives which
tell Gregorio to do something specific, then raising an error when
there's an unrecognized one is important because it tells the user that
their directive is malformed and needs to be fixed.
Right now we have a mix of headers. Examples:
"language" is a directive, telling Gregorio how to determine the vowel
in a syllable.
"annotation" could be considered both. It's a directive in that
Gregorio uses it to pass on annotations to the gtex file, but those
annotations are themselves metadata about the score.
"manuscript" is pure metadata. While Gregorio recognizes it currently,
it doesn't do anything with the contents.
Perhaps what is needed is some sort of separation between the two sorts
of headers so that we can differentiate between headers which the user
should expect to effect their output (and on which we raise errors if
things aren't kosher) and those which don't (and which Gregorio can
safely ignore at runtime).
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel
