Open ahinkley opened 2 years ago
Our general strategy has been to move towards a more strict separation between musical content (which stays in the gabc) and the visual appearance (which is managed in TeX) whenever possible. Choosing the font is decidedly an appearance issue, and so something we'd prefer to handle in TeX. Do you have any musical reason for preferring Laon neumes over any other set of ancient notation neumes?
I'm employed by the Neumz project to add the Laon neumes to their GABC files, it's a feature they intend to add in the future. I'll also be adding St. Gall, after I've finished transcribing the Laon neumes.
That's a practical reason. By musical reason I mean is there some reason why a nabc notation derived from one source not be rendered using the notation (font) of another source (disregarding incomplete coverage issues in one or the other fonts)?
There's not really a musical reason. The intention is to offer both notations.
You should be able to use \gresetheadercapture
and set the NABC font that way. Untested theoretical code:
In the gabc file have the header line user-notes: grelaon;
In the TeX file:
\newcommand{\setnabcfont}[1]{\gresetnabcfont{#1}{10}}
\gresetheadercapture{user-notes}{setnabcfont}{}
At the moment I use \gresetnabcfont{grelaon}{10} in the TeX wrapper file to specify that I want to use Laon neumes. Would it be possible to do this with a GABC header instead? It would be nice if I could have a header like nabc-font:laon;