On Thursday, 24 December 2015 at 11:59:35 am -0500, Br. Samuel Springuel wrote: > 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: > ... cut for brevity ... > > 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).
My suggestion is that we support "x-" headers that allow the user to add any custom headers they want to the gabc file. These will be gathered, kept, and re-emitted, but they have no semantic meaning to the gregorio system. No error or warning will be produced for an "x-" header. Any other header will be considered a semantic header (even if we don't do anything with it right now), so if it's not valid, an error (or maybe a warning?) will be produced. Henry _______________________________________________ Gregorio-devel mailing list [email protected] https://mail.gna.org/listinfo/gregorio-devel
