Re: Tie properties vs. slur properties.

> The tie interface has height-limit and ratio as part of Tie.details. > > The slur interface has height-limit and ratio as part of Slur (not > embedded in Slur.details). > > Is there a reason for this difference, or is it just due to never > making the two be consistent? I believe it's the

Tie properties vs. slur properties.

The tie interface has height-limit and ratio as part of Tie.details. The slur interface has height-limit and ratio as part of Slur (not embedded in Slur.details). Is there a reason for this difference, or is it just due to never making the two be consistent? If there is no reason for the

Re: scriptDefinitions context property

On Tue, May 24, 2016 at 7:12 PM, Carl Sorensen wrote: > According to the Internals Reference, scriptDefinitions is an internal > context property, meaning that the user should not change it. > > Why is this so? As far as I can see, scriptDefinitions is not defined > during

scriptDefinitions context property

According to the Internals Reference, scriptDefinitions is an internal context property, meaning that the user should not change it. Why is this so? As far as I can see, scriptDefinitions is not defined during engraving, but during initialization. So it ought to be user-settable, it seems to

Re: Add halfopenvertical to script.scm (issue 297340043 by carl.d.soren...@gmail.com)

On 2016/05/24 23:57:38, Carl wrote: The challenge is that some of the feta font elements in the scripts.* familiy are used as articulations, while others (e.g. caesura) are not. And the ones not used as articulations are not included in script.scm by choice. I guess my wording was bad.

Re: Add halfopenvertical to script.scm (issue 297340043 by carl.d.soren...@gmail.com)

Reviewers: thomasmorley651, Message: It seems to me that if we want to make this kind of a regtest we should really be looking at all TextScripts that are supposed to be articulations, and seeing if the articulations work. The regtest you proposed looks at all the articulations we have defined,

Re: broken doc build (orchestra.ly)

James writes: > David > > On 24/05/16 18:20, David Kastrup wrote: >> James Lowe writes: >> >>> No core file was generated, I also upped the ulimit to 1GB. >>> >>> So perhaps it isn't the type of 'assertion' or crash you thought it >>> was after all? >> Perhaps.

Re: broken doc build (orchestra.ly)

David On 24/05/16 18:20, David Kastrup wrote: James Lowe writes: No core file was generated, I also upped the ulimit to 1GB. So perhaps it isn't the type of 'assertion' or crash you thought it was after all? Perhaps. Knut's problem, however, sounded like it. If you have

Re: broken doc build (orchestra.ly)

David On 24/05/16 18:20, David Kastrup wrote: James Lowe writes: No core file was generated, I also upped the ulimit to 1GB. So perhaps it isn't the type of 'assertion' or crash you thought it was after all? Perhaps. Knut's problem, however, sounded like it. If you have

Re: broken doc build (orchestra.ly)

James Lowe writes: > No core file was generated, I also upped the ulimit to 1GB. > > So perhaps it isn't the type of 'assertion' or crash you thought it > was after all? Perhaps. Knut's problem, however, sounded like it. If you have different results from Knut, things are even

PATCHES: Countdown for May 24th

Hello, Here is the current patch countdown list. The next countdown will be on May 27th. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ __ Push: 4850 Remove self method bindings of translator groups - David