Lyrics touching notes or clef below

[Matthew Roth]

Hello all,

As you can see, the torculus (klk) doesn't have enough room; the page break occurs before the instance in the first verse, as it happens.

Or the letter "p" or old-style verse numbers that sit low hit a clef or come a bit too close.

Am I looking at \grechangenextscorelinedim or \grechangecount, and which string should be used? (I'm usually very happy with the default settings, but as I typeset more, I'm seeing funny things like this more often, and have confused myself after reading the documentation.) Thank you!

[Fr. Samuel Springuel]

If you’re looking to change just the one line, then `\grechangenextscorelinedim` is the command to invoke. You’re probably looking to change spacebeneathtext which controls, not surprisingly, the space beneath the text.

Though to be honest, I’m surprised that things are that tight by default, especially for the high torculus. I would have expected the high torculus to force it line down a bit more. Did you run the compilation process once or twice? Line heights are adjusted on the second pass because on the first pass we don’t yet know which high notes and which low notes will be on which line. The first pass figures out which lines have high and low notes and records that so that the second pass can adjust the line heights appropriately.

✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Fr. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036

PAX ☧ ΧΡΙΣΤΟΣ

> On Mar 10, 2024, at 5:05 PM, Matthew Roth <roth.m...@gmail.com> wrote:
>
> Hello all,
>
> As you can see, the torculus (klk) doesn't have enough room; the page break occurs before the instance in the first verse, as it happens.
>

> Or the letter "p" or old-style verse numbers that sit low hit a clef or come a bit too close.<Screenshot 2024-03-10 at 16.00.36.png>

> <Screenshot 2024-03-08 at 12.51.28.png>
> Am I looking at \grechangenextscorelinedim or \grechangecount, and which string should be used? (I'm usually very happy with the default settings, but as I typeset more, I'm seeing funny things like this more often, and have confused myself after reading the documentation.) Thank you!
>

> --
> Gregorio homepage: http://gregorio-project.github.io
> Archives for the old mailing list: http://www.mail-archive.com/gregori...@gna.org/
> To report a bug, please post to: https://github.com/gregorio-project/gregorio/issues
> ---
> You received this message because you are subscribed to the Google Groups "Gregorio Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gregorio-user...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gregorio-users/1df6d82e-a4c0-463c-8c8f-788aef1d60bfn%40googlegroups.com.
> <Screenshot 2024-03-08 at 12.51.28.png><Screenshot 2024-03-10 at 16.00.36.png>

[Matthew Roth]

This is after multiple passes in each document…

 I’ll try it again to see if it goes away and then tinker.

[Matthew Roth]

On further review: yep, I definitely have run the Te Lucis example (so the one with the torculus) twice, as I ran latexmk which took into account things which require a second pass. I hate using a magic number here for the , but here we are, and I had the same thought, i.e. that the default settings should account for that torculus…

\grechangenextscorelinedim{3,5}{spacebeneathtext}{0.1cm}{scalable} fixes the torculus problem, but it gives me a clash with the podatus on line 4 (it collides with the comma).

OK, so then I include that line. \grechangenextscorelinedim{3,4,5}{spacebeneathtext}{0.1cm}{scalable}. That fixes the podatus and second torculus, but the first one on line 3 of the score, is back to being stuck under the text. And I've run both multiple times.

If there's a solution that gives spacebeneathtext more room for the whole score (with or without knowing how many lines I need) then I'm also all ears…