Re: Bad slur shape at line break with change of clef

2020-12-13 Thread Thomas Morley
Am So., 13. Dez. 2020 um 16:56 Uhr schrieb James Lowe : > > On 13/12/2020 15:29, Jonas Hahnfeld via bug-lilypond wrote: > > Hi all, Harm, > > > > Am Sonntag, dem 13.12.2020 um 13:53 +0100 schrieb Thomas Morley: > >> Hopefully somebody with more knowledge, chimes in. > > Could you create a GitLab

Re: Web site bug? -- OOoLilyPond

2020-12-13 Thread James Lowe
On 05/12/2020 11:16, Klaus Blum wrote: Dear List members, Hello, In the “Easier editing” page [1], OOoLilyPond is listed in the “Other programs no longer being actively developed” section but I think that it is active again. Is this considered as a documentation bug?

Re: Bad slur shape at line break with change of clef

2020-12-13 Thread James Lowe
On 13/12/2020 15:29, Jonas Hahnfeld via bug-lilypond wrote: Hi all, Harm, Am Sonntag, dem 13.12.2020 um 13:53 +0100 schrieb Thomas Morley: Am Sa., 12. Dez. 2020 um 21:07 Uhr schrieb Timothy Lanfear : The part of the slur before the line break is badly shaped when another staff has a clef

Re: Bad slur shape at line break with change of clef

2020-12-13 Thread Jonas Hahnfeld via bug-lilypond
Hi all, Harm, Am Sonntag, dem 13.12.2020 um 13:53 +0100 schrieb Thomas Morley: > Am Sa., 12. Dez. 2020 um 21:07 Uhr schrieb Timothy Lanfear > : > > > > The part of the slur before the line break is badly shaped when another > > staff has a clef change. > > > > \version "2.20.0" > > > > << > >

Re: Bad slur shape at line break with change of clef

2020-12-13 Thread Thomas Morley
Am Sa., 12. Dez. 2020 um 21:07 Uhr schrieb Timothy Lanfear : > > The part of the slur before the line break is badly shaped when another > staff has a clef change. > > \version "2.20.0" > > << >\new Staff { > R1*2 > r2 r4 r8 r16 r32 e''32( | > \break > d''8) r r4 r2 | >