Here is a concrete proposal:

Change the handling of gabc header fields so that a header field ends
at either ;^J (semicolon immediately followed by a newline), on the
same line as the header keyword;  or ;; (two semicolons), anywhere.

This allows for 

- semicolons in field values;

- multi-line values where necessary.

Currently gregorio allows multi-line values (though it's not
documented) but not semicolons in fields.

Examples: (all current example headers work as now)

user-notes: a one line example; but with a semicolon in it;

user-notes: this example has 
three
lines;;

user-notes: this example has three lines
and the last has a trailing newline
which may be neater
;;

-- 
David Stone

_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel

Répondre à