Enhancement: Take ‘master’ line thickness from a context property [was: Re: list of thicknesses…]

2016-01-31 Thread Simon Albrecht
On 31.01.2016 23:15, Simon Albrecht wrote: On 31.01.2016 22:34, Kieren MacMillan wrote: Ultimately, my goal is to be able to design stylesheets that match certain “house styles” (e.g., Hanle, Chappell & Co., Peters). I find that many plate-engraved scores appear to have a slightly heavier over

Re: Bad clef change collision when alternating piano staves

2016-01-31 Thread Ophir Lifshitz
Hello, Would it be possible to triage this bug I reported 3 months ago? Thanks, Ophir On Fri, Jan 1, 2016 at 10:03 AM, Ophir Lifshitz wrote: > Hello again, > > Has anyone been able to triage this bug yet? > > Thanks, > Ophir > > On Wed, Oct 28, 2015 at 11:31 AM, Ophir Lifshitz < > hangfromthef

Re: StaffSymbol.thickness affects bar number position

2016-01-31 Thread Colin Campbell
On 16-01-31 01:47 PM, Noeck wrote: Hi, changing the thickness of staff lines has known (and intended) side effects on stems etc. But it should not move the bar numbers as shown here: { \override Staff.StaffSymbol.thickness = 3 a1 \break a } Could someone open an issue for that? Cheers,

StaffSymbol.thickness affects bar number position

2016-01-31 Thread Noeck
Hi, changing the thickness of staff lines has known (and intended) side effects on stems etc. But it should not move the bar numbers as shown here: { \override Staff.StaffSymbol.thickness = 3 a1 \break a } Could someone open an issue for that? Cheers, Joram ___

Re: No warning upon failed ‘align[Above|Below]Context’

2016-01-31 Thread Simon Albrecht
On 30.01.2016 00:49, Simon Albrecht wrote: Hello, in this example %%% \version "2.19.35" \new StaffGroup << \new Staff = "A" { a'1 a' } { \skip 1 \new Staff = "C" \with { alignAboveContext = "B" } { c''1 } } { \skip 1 \new Staff = "B" \with { alignAboveContext = "A" } { b'1 } } >>

Re: Kneed beam and subdivisions

2016-01-31 Thread Gilberto Agostinho
Gilberto Agostinho wrote > I also would like to offer a small bounty to get this fixed: I can pay 30 > EUR to anyone who is able to fix this until February 2016. I know that > giving a deadline for a bounty isn't really the most elegant thing to do, > but this issue is greatly affecting my final wo