Le 13/06/2022 à 07:31, Werner LEMBERG a écrit :
I see that the function also listens to `basic-distance` (probably
from `VerticalAxisGroup`), but I wasn't able to trigger it – most
probably, this code part is not specific to figured bass.
I think this should do (I can elaborate when I have
>> I see that the function also listens to `basic-distance` (probably
>> from `VerticalAxisGroup`), but I wasn't able to trigger it – most
>> probably, this code part is not specific to figured bass.
>
> I think this should do (I can elaborate when I have more time):
>
> \version "2.22.2"
>
>
Jean Abou Samra writes:
[...]
> staff-padding also works for this purpose. However, it may be trumped by
> other settings if they lead to larger offset values. You likely need
> to reduce padding and outside-staff-padding. This changes the spacing
> in situations where there are collisions.
Hi Jean,
Thanks for this really in-depth explanation! Despite having used Lilypond for
twenty years, and RTFineM[s] multiple times, in great depth, your
analysis/presentation contained new information/insights for me.
> If a letter protrudes on the bottom like "g"
> (not sure how this would be
OK, trying to correct myself and articulate a little more coherent
thoughts this time. Sorry, I was hearing about election results in
France at the same time and was distracted.
I wrote:
Le 12/06/2022 à 21:32, Jean Abou Samra a écrit :
Le 12/06/2022 à 21:08, Kieren MacMillan a écrit :
Hi
Hi Jean,
Sorry I didn’t respond to this:
> For a start, this can be useful:
> {
> \override Score.RehearsalMark.Y-offset = 4
> \mark \markup { agt } g'1
> \mark \markup { aht } g'1
> \mark \markup { agt } g'1
> }
Well, yes… and I’ve used that mechanism in my scores. My frustration is
Hi Jean,
> I don't understand how staff-padding relates to this discussion.
It relates to the discussion as follows:
— when one wants to align TextScripts above the staff to their baseline(s), one
apparently uses staff-padding;
— when one wants to align RehearsalMarks (or, probably,
p.s. To be clear, \override-ing Score.RehearsalMark.staff-padding does nothing,
which is a related but separate point of inconsistency.
— Kieren
> On Jun 12, 2022, at 3:37 PM, Kieren MacMillan
> wrote:
>
> Hi all,
>
> Sorry for the typo in the last email… Here’s a “correct incantation”:
>
Hi all,
Sorry for the typo in the last email… Here’s a “correct incantation”:
\version "2.23.4"
{
\override Score.RehearsalMark.padding = #2
\mark \markup { agt } g'1
\mark \markup { aht } g'1
\mark \markup { agt } g'1
}
I put “correct incantation” in quotes because it moves the
Le 12/06/2022 à 21:32, Jean Abou Samra a écrit :
Le 12/06/2022 à 21:08, Kieren MacMillan a écrit :
Hi David,
I have problems believing we did not have this particular discussion
already since there is a documented setting for it.
I don't understand how staff-padding relates to this
Le 12/06/2022 à 21:08, Kieren MacMillan a écrit :
Hi David,
I have problems believing we did not have this particular discussion
already since there is a documented setting for it.
I don't understand how staff-padding relates to this discussion.
It counts from the reference point of the
Hi David,
> I have problems believing we did not have this particular discussion
> already since there is a documented setting for it.
The problem isn’t really whether there’s a documented setting or not… It’s
whether that documented setting is consistently applied and behaves in the way
most
Kieren MacMillan writes:
> Hi Jean,
>
>> Then I don't understand the problem. What characteristic
>> of baseline-skip do you wish? Is it that it counts from
>> the origin of each markup and somehow this distance is
>> more convenient for you to provide? Is it that it ignores
>> the extents of
Le 12/06/2022 à 19:11, Werner LEMBERG a écrit :
This sounds like it might be related to my [long-standing] concerns
about leading, etc., in markups: there either isn’t a convenient
mechanism to deal with texts/markups *from their baseline [and not
their reference point]*, or the convenient
> This sounds like it might be related to my [long-standing] concerns
> about leading, etc., in markups: there either isn’t a convenient
> mechanism to deal with texts/markups *from their baseline [and not
> their reference point]*, or the convenient mechanism exists and
> isn’t sufficiently well
> Then I don't understand the problem. What characteristic of
> baseline-skip do you wish? Is it that it counts from the origin of
> each markup and somehow this distance is more convenient for you to
> provide? Is it that it ignores the extents of the markups?
I want equal vertical spacing of
Hi Jean,
> Then I don't understand the problem. What characteristic
> of baseline-skip do you wish? Is it that it counts from
> the origin of each markup and somehow this distance is
> more convenient for you to provide? Is it that it ignores
> the extents of the markups?
>
> Could you explain
Le 12/06/2022 à 17:55, Werner LEMBERG a écrit :
Nope, this only changes the padding (i.e., the whitespace between the
bottom of the upper and the top of the lower element). What I want is
vertical stacking as if it were done with the `\column` markup command
– which respects `baseline-skip`.
>> Consider the following example:
>>
>> ```
>> \figures {
>>
>> }
>> ```
>>
>> As can be seen in the attached image, the elements are separated by
>> padding only; they are not vertically spaced using `baseline-skip`
>> or something similar.
>>
>> How can I change that?
>
> Like this?
>
>
Le 12/06/2022 à 17:36, Werner LEMBERG a écrit :
Consider the following example:
```
\figures {
}
```
As can be seen in the attached image, the elements are separated by
padding only; they are not vertically spaced using `baseline-skip` or
something similar.
How can I change that?
Consider the following example:
```
\figures {
}
```
As can be seen in the attached image, the elements are separated by
padding only; they are not vertically spaced using `baseline-skip` or
something similar.
How can I change that?
Werner
21 matches
Mail list logo
