Hi Aaron (et al.),
Thanks to your "trim-descenders" function, the output is as follows:
The carets all line up — because the text baselines do — WITH NO INDIVIDUAL
TWEAKS REQUIRED! Taking tweak-and-recompile time into account, that probably
saves me an hour over the course of engraving a scor
Hi Aaron,
> Your issue is that the padding between staff and markup is using the bottom
> extent, not the baseline, hence it looks off.
Exactly. And this is generally true of markup/text, I’ve found.
> You might just want to clip the descenders on offending lines.
Interesting! That works well
On 2018-11-17 9:05 am, Kieren MacMillan wrote:
Hi Aaron,
Ah, but the 7 and 5 in that font in fact have descenders. The
baseline is not the same as the bottom extent of a glyph.
Yes — we’re saying the same thing. =)
Oh, I'm a dumb dumb.
Your issue is that the padding between staff and mar
Hi David,
> Have you tried using staff-padding ?
Yes. Here’s the same code with #'staff-padding = #3:
In this case, that’s a Beam the Fingerings are set above, which is itself *far*
above the actual Staff. So #'padding is being applied, and we’re nowhere near
close enough for #'staff-padding
Hi Aaron,
> Ah, but the 7 and 5 in that font in fact have descenders. The baseline is
> not the same as the bottom extent of a glyph.
Yes — we’re saying the same thing. =)
> For reference, what is the font you are using?
Alegreya.
Thanks,
Kieren.
Kieren Mac
Kieren MacMillan writes:
> I assume the padding is using the lower edge of the glyph outline
> (i.e., the blue box) to align; and that perfectly matches the output
> as seen. What I *want* is the ability to set text/markup padding to
> the *baseline*. It doesn’t ever seem to be possible, which fo
On 2018-11-17 8:50 am, Kieren MacMillan wrote:
Here’s a screenshot from the actual score I’m trying to engrave, with
your function in place (minus the text duplication):
Notice that the triangles of each figure are as hoped/expected… but
the *actual baseline of the glyph* is not being honoured c
Hi Aaron,
WOW! Thanks for this. So interesting.
Recall that earlier in the thread, I said "Bonus points if [the fix] handles
lowercase numerals"? ;)
Here’s a screenshot from the actual score I’m trying to engrave, with your
function in place (minus the text duplication):
Notice that the tr
On 2018-11-17 4:39 am, Kieren MacMillan wrote:
I really don’t understand why Lilypond’s text handling is so fussy. It
should be easy for the user to say “lines in a multi-line markup must
be exactly *this* far apart [regardless of individual glyph height]” —
in fact, it should be the default.
A
Hi Thomas,
Thanks for trying.
I really don’t understand why Lilypond’s text handling is so fussy. It should
be easy for the user to say “lines in a multi-line markup must be exactly
*this* far apart [regardless of individual glyph height]” — in fact, it should
be the default.
Cheers,
Kieren.
Am Sa., 17. Nov. 2018 um 12:03 Uhr schrieb Thomas Morley
:
> Default \center-column does not adjust baseline-skip according to the
> grobs font-size.
> Below I wrote 'center-column-fontsize-adjusted-baseline-skip' (you
> should probably rename it, lol), which does so. Modeled after how
> \fontsize
Hi Kieren,
Am Sa., 17. Nov. 2018 um 02:36 Uhr schrieb Kieren MacMillan
:
>
> Hi all,
>
> In the snippet below, you’ll see that I’m attempting to override Fingering in
> a custom context to add a caret (^) on top of the [formatted] finger number
> to make it into a scale degree.
>
> The "padding"
Hi all,
In the snippet below, you’ll see that I’m attempting to override Fingering in a
custom context to add a caret (^) on top of the [formatted] finger number to
make it into a scale degree.
The "padding" between the caret and the number isn’t relative, as I would like
it to be: it should a
13 matches
Mail list logo
