> The reason is, it appears that old notation fonts have become
> slightly broken, especially glyphs relating to numbers (time
> signatures, multi-measure rests, figured bass). The attached files
> are rendered in 2.25.2 and .16 using
> https://github.com/OpenLilyPondFonts/cadence .
I've just tri
> I came across LSR #304 https://lsr.di.unimi.it/LSR/Item?id=304 and I
> think we should suggest a coding with variables there, like this:
> [...]
Yes, LilyPond should be both more supportive and more 'user friendly'
here; this is tracked as
https://gitlab.com/lilypond/lilypond/-/issues/6525
On Fri, 12 Jul 2024 at 06:11, Tom Brennan wrote:
> Hi all
>
> When using `\magnifyStaff #2/3`, I'm seeing weird transitions between the
> staves of a `StaffGroup`. For example,
>
> ```
> \version "2.24.3"
>
> music = \relative c'' {
> \repeat unfold 10 { c4 d e f } \bar "||" c d e f \bar "|."
Dear list,
I was wondering if anyone could help me with the changes to the notation
font in 2.25.x?
I was looking for a list of changes to the emmentaler font but could not
find it in
https://lilypond.org/doc/v2.25/Documentation/changes/index.html . The
reason is, it appears that old notati
Hello,
I came across LSR #304 https://lsr.di.unimi.it/LSR/Item?id=304 and I
think we should suggest a coding with variables there, like this:
%%
startTrillSpanSharp =
-\tweak bound-details.left.text
\markup { \musicglyph "scripts.trill" \raise #0.65 \teeny \sharp }
This is a well-known problem and you can find several alternative
work-arounds in the manual, see
https://lilypond.org/doc/v2.24/Documentation/notation/setting-the-staff-size
/Mats
On 2024-07-11 22:09, Tom Brennan wrote:
Hi all
Hello William,
this works out totally fine. It’s just that with that very tight spacing
Lilypond’s merit algorithm cannot have the Slur go from head to head. Say if
we drastically increase the demerit for distance to the edge points:
%%%
\score {
<<
\new Staff = "a" {
\override Slur
