I could have thought of that... Thanks David for the tip and Jean for
opening the issue. I'll use the workaround until then...
Le vendredi 13 janvier 2023 à 14:03, David Wright a écrit :
> On Fri 13 Jan 2023 at 19:30:29 (+), nitra...@posteo.net wrote:
> > I was talking about the first note of
Le 13/01/2023 à 10:16, Werner LEMBERG a écrit :
Regardless of that, it is indeed a severe bug: No need to ever align
key signatures vertically, AFAIK. Simply left-align them.
I have opened an issue for this:
https://gitlab.com/lilypond/lilypond/-/issues/6520
OpenPGP_signature
Description:
On Fri 13 Jan 2023 at 19:30:29 (+), nitra...@posteo.net wrote:
> I was talking about the first note of each measures after the Key Signature.
> But you were right, it is the default spacing.
>
> About the distance between different accidentals, consider the example
> bellow. You can see a
I was talking about the first note of each measures after the Key Signature.
But you were right, it is the default spacing.
About the distance between different accidentals, consider the example
bellow. You can see a difference between the "Reference staff" and number
"C" in the "Corrected
On Fri 13 Jan 2023 at 11:58:42 (+), nitra...@posteo.net wrote:
> Yes it is better, thank you for your fast reply. But several problems are
> still there in my opinion:
>
> - The first note of the measure doesn't align with the last accidental and
> is still too far.
None of the first notes
Yes it is better, thank you for your fast reply. But several problems are
still there in my opinion:
- The first note of the measure doesn't align with the last accidental and
is still too far.
- I don't understand why the distance between different accidentals is
wider (for instance between
Le 13/01/2023 à 10:16, Werner LEMBERG a écrit :
I just discovered this huge bug in the recent release of 2.24.0
which wasn't in the previous version.
What previous version did you test this with? For me, the output is
the same in 2.22 and in 2.18.2.
Regardless of that, it is indeed a severe
>> I just discovered this huge bug in the recent release of 2.24.0
>> which wasn't in the previous version.
>
> What previous version did you test this with? For me, the output is
> the same in 2.22 and in 2.18.2.
Regardless of that, it is indeed a severe bug: No need to ever align
key
