Re: 5027: NR example with bad engraving practice

2017-01-06 0:04 GMT+01:00 Hans Aikema : > >> On 5 Jan 2017, at 23:55, Simon Albrecht wrote: >> >> On 05.01.2017 23:42, Hans Aikema wrote: On 5 Jan 2017, at 23:16, Simon Albrecht wrote: >> On 04.01.2017 15:01, Hans

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

Thomas Morley writes: > 2017-01-04 16:01 GMT+01:00 Chris Yate : >> On Wed, 4 Jan 2017 at 14:25 Thomas Morley wrote: > >> Well, it's odd. I'm not sure this is anything to do with /overrideProperty. >> >> Referring back to

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

On Fri, 6 Jan 2017 at 11:34 David Kastrup wrote: > > Assertions should not be used when LilyPond has a sane way to continue: > for that case, programming errors are more appropriate. The question is > whether this is the case here: I think we are also dealing with bad > output

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

On Fri, 6 Jan 2017 at 12:31 David Kastrup wrote: Chris Yate writes: > On Fri, 6 Jan 2017 at 11:34 David Kastrup wrote: > >> >> Assertions should not be used when LilyPond has a sane way to continue: >> for that case, programming errors are more

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

2017-01-04 16:01 GMT+01:00 Chris Yate : > On Wed, 4 Jan 2017 at 14:25 Thomas Morley wrote: > Well, it's odd. I'm not sure this is anything to do with /overrideProperty. > > Referring back to my original tests, I can change your definitions to the >

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

2017-01-06 12:34 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> 2017-01-04 16:01 GMT+01:00 Chris Yate : >>> On Wed, 4 Jan 2017 at 14:25 Thomas Morley wrote: >> >>> Well, it's odd. I'm not sure this is

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

On Fri, 6 Jan 2017 at 10:23 Thomas Morley wrote: > 2017-01-04 16:01 GMT+01:00 Chris Yate : > > On Wed, 4 Jan 2017 at 14:25 Thomas Morley > wrote: > > > Well, it's odd. I'm not sure this is anything to do with >

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

2017-01-06 13:10 GMT+01:00 Chris Yate : > Curiously, this didn't fail with assertions. I've just upgraded to 2.19.54, > and the test cases that crashed for me previously still crash :) Could you remove all "Test 3x"-scores from the test-file and redo compilation, please.

New Catalan PO file for 'lilypond' (version 2.19.54)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Catalan team of translators. The file is available at: http://translationproject.org/latest/lilypond/ca.po (We can arrange things so

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

2017-01-06 13:10 GMT+01:00 Chris Yate : > > Curiously, this didn't fail with assertions. I've just upgraded to 2.19.54, > and the test cases that crashed for me previously still crash :) > > Log attached (although I don't think this will be very helpful). Strange that your

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

Chris Yate writes: > On Fri, 6 Jan 2017 at 11:34 David Kastrup wrote: > >> >> Assertions should not be used when LilyPond has a sane way to continue: >> for that case, programming errors are more appropriate. The question is >> whether this is the case here:

Re: [2.20] Issue 4943 Manual page breaking causing assertion failure using Windows

On Fri, 6 Jan 2017 at 12:23 Thomas Morley wrote: > 2017-01-06 13:10 GMT+01:00 Chris Yate : > > > > > Curiously, this didn't fail with assertions. I've just upgraded to > 2.19.54, > > and the test cases that crashed for me previously still crash :) >