On Mon, Jun 20, 2016 at 06:48:52PM +0200, Infermeria Abbazia Mater Ecclesiae
wrote:
> Dear All,
>
> I'm trying to add some complex nabc lines to gabc scores, trying to mantain
> a semi-diastematic writing (i.e. to preserve relative neumes height),
> copying neumes directly from manuscript sources.
> I don't know if I'm missing something but I noticed that:
> 1. I'm often forced to decide glyphs height only at the end of the encoding
> (and that's not a problem, actually), but doing this way, I get odd spacing
> between nabc and gabc lines (that is: too much empty space between the two:
> see line 1 in the attached example);
> 2. When a neume starts with a flat in gabc, the nabc related code seems to
> be aligned on the flat, and I'm not able to move it further (adding /// for
> instance).
>
> So, my question:
> A. Is it possible to define a macro to tune the basic nabc line, something
> like:
> \grechangespace{nabcbaselineheight}{x}
> where "x" is the vertical distance added (or subtracted) between nabc and
> the gabc staff?
> B. What should I do to "force" a glyph alignment in nabc code and put it
> exactly on the note I want?
Right now the St. Gall neumes above staff are emitted using the same
infrastructure as <alt>...</alt>, so for the spacing in between the base
line of the neumes and the staff or between the top of them and previous
staff/line of text applies whatever can be used for <alt>.
The vertical spacing within nabc is done through ha - hn and hp, hf is
the default, and each letter is 1/4 of the font's height metrics.
The horizontal spacing is tunable through
nabcinterelementspace and nabclargerspace.
For flats, I'm usually using /// and that works fine for me, like:
í(ghGF|``pe-1su2lse4)ta(ix-ghgh/i|///tr-1vihi)que(h|vi)
At the expense of breaking backwards compatibility, we perhaps could in some
future release move the default for flats and natural so that it would
default to starting after the flat/natural and in the less likely case
that one wants to place the neume horizontally earlier, one would need to
use `, `` or ``` etc., but that is likely too late for 4.2 now.
Except for flats/naturals, otherwise the particular nabc neume start should
be aligned with the corresponding gabc neume below it.
For shorter neumes I usually use just one | inside of (), and only for
longer melismas split it into multiple |s, e.g.:
(gih/|to-1|giHG'|toS2hgsut1|gd/|pihhsut1lst2|efED|pehisu2lsc2|dc/|pilst2|de/feed.|clppu2lst2pi)
If gabc contains /s, they should be better at the end of the gabc pieces
rather than at their start, so e.g. in the above better:
(gih/|to-1|giHG'
than
(gih|to-1|/giHG'
OT, started working on grelaon font, so far by collecting pictures of the
various glyphs, have 256 of them by now (including various Tironian marks),
and will start soon with painting that into a font. But once that is done,
we'll need to resolve placement of nabc neumes also in between staff and
lyrics, support nabc-lines: > 1 and have some way perhaps in *.gabc header
to say which of the nabc pieces is St. Gall and which is Messine notation.
Jakub
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users
