Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread David Kastrup
Pavel Roskin writes: > On Wed, 19 Jun 2013 18:00:09 +0200 > David Kastrup wrote: > >> Pavel Roskin writes: >> >> > Quoting David Kastrup : >> > >> >> Pavel Roskin writes: >> >> >> >>> I just hope you won't take away the ability to adjust the key >> >>> signature without placing the accidental

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread Pavel Roskin
On Wed, 19 Jun 2013 18:00:09 +0200 David Kastrup wrote: > Pavel Roskin writes: > > > Quoting David Kastrup : > > > >> Pavel Roskin writes: > >> > >>> I just hope you won't take away the ability to adjust the key > >>> signature without placing the accidentals manually. > >> > >> It would appea

Change clef on grace silent rest has no horizontal space

2013-06-19 Thread Pavel Roskin
Hello! David Kastrup asked me to report this bug earlier today. This is a simplified example. \version "2.17.20" { \grace { s4 } \clef bass c'4 } The bass clef collides with the time signature. Also, the note is positioned too close to the bass clef. The note position would be OK if the b

Re: If incipit has soprano clef, its staves are not aligned with main score

2013-06-19 Thread Marek Klein
Hello, 2013/6/12 Pothárn Imre > > I'm not top posting. > > % When the incipit has a soprano clef, > % the staff lines are not aligned > % irrespective of the clef of main part > Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3416 Marek bug s

Re: Weird Stems with beam::align-with-broken-parts and beam::slope-like-broken-parts

2013-06-19 Thread Marek Klein
Hello, 2013/6/14 Thomas Morley > Hi, > > the following code returns missing Stems. > (A larger example would show not only missing but also all sorts of weird > Stems. > see: > http://lists.gnu.org/archive/html/lilypond-user/2013-06/msg00334.html > ) Thank you for the report, this has been add

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread David Kastrup
Pavel Roskin writes: > Quoting David Kastrup : > >> Pavel Roskin writes: >> >>> I just hope you won't take away the ability to adjust the key >>> signature without placing the accidentals manually. >> >> It would appear that you can adjust the key signature just fine by using >> the _intended_ c

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread Pavel Roskin
Quoting David Kastrup : Pavel Roskin writes: I just hope you won't take away the ability to adjust the key signature without placing the accidentals manually. It would appear that you can adjust the key signature just fine by using the _intended_ context variables for that. If you mean so

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread David Kastrup
Pavel Roskin writes: > Quoting David Kastrup : > >> Pavel Roskin writes: >> >>> By the way, setting KeySignature.c0-position with \override doesn't >>> work. I had to resort to setting it in Scheme: >> >> Given the analysis in a longer mail, I revert my opinion that we need to >> do something

\omit Dots acts like \hide Dots

2013-06-19 Thread Pavel Roskin
Hello! \omit Dots should not reserve space for the omitted dots. That's what \hide does. The problems exists in Lilypond 2.16 as well. The \omit keyword just makes it more obvious that the current behavior is wrong. \version "2.17.20" \score { << \new Staff << \new Voice

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread Pavel Roskin
Quoting David Kastrup : Pavel Roskin writes: By the way, setting KeySignature.c0-position with \override doesn't work. I had to resort to setting it in Scheme: Given the analysis in a longer mail, I revert my opinion that we need to do something here. c0-position for the relevant grobs _c

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread David Kastrup
Pavel Roskin writes: > Quoting David Kastrup : > >> Small wonder. I thought our default use of symbols matched our naming >> rules, but that one's an exception. >> >> We can make an exception for convert-ly here, but that's not a >> satisfactorily final solution. >> >> I propose renaming it. Su

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread David Kastrup
Pavel Roskin writes: > Quoting David Kastrup : > >> Small wonder. I thought our default use of symbols matched our naming >> rules, but that one's an exception. >> >> We can make an exception for convert-ly here, but that's not a >> satisfactorily final solution. >> >> I propose renaming it. Su

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread Pavel Roskin
Quoting David Kastrup : Small wonder. I thought our default use of symbols matched our naming rules, but that one's an exception. We can make an exception for convert-ly here, but that's not a satisfactorily final solution. I propose renaming it. Suggestions? I'm fine with renaming. We ha

Re: convert-ly produces invalid output for KeySignature.c0-position

2013-06-19 Thread David Kastrup
Pavel Roskin writes: > Hello! > > I'm using the current lilypond from git. This is what I have before > the conversion: > > \version "2.16.0" > { > \override KeySignature #'c0-position = #6 > } > > convert-ly turns it into: > > \version "2.17.20" > { > \override KeySignature.c0-position = #6