Re: stopStaff combined with StaffGroup extents barlines

I forward your question to bug-lilypond, since it shows a regression bug compared to earlier versions. /Mats Toine Schreurs wrote: I am typesetting a score, where one of the staffs contains an ossia section. I started from the example in section 1.6.1 of the NR. The second staff will contain

Issue 569 in lilypond: Consistency in property names: beam-thickness

Issue 569: Consistency in property names: beam-thickness http://code.google.com/p/lilypond/issues/detail?id=569 New issue report by v.villenave: Currently, the beam-thickness property is only used for StemTremolo objects. It might be better to change the property name for the thickness of all

Issue 570 in lilypond: Articulations can collide with ties

Issue 570: Articulations can collide with ties http://code.google.com/p/lilypond/issues/detail?id=570 New issue report by v.villenave: % another collision involving ties: \version 2.11.38 \paper { ragged-right = ##t } \relative c'' { f-- f~-- f~ } Issue attributes:

Re: articulations collide with ties

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=570 Cheers, Valentin On 03/02/2008, Andrew Hawryluk [EMAIL PROTECTED] wrote: I couldn't find this one on the bug list: articulations can collide with ties. \version 2.11.38 \paper { ragged-right = ##t } \relative

Re: horizontal spacing problem in grace notes below the staff

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=571 You full report is quite accurate, however I just added a link to it in order to preserve the holy minimal-reports-only-policy-thing (TM). Cheers, Valentin On 03/02/2008, Andrew Hawryluk [EMAIL PROTECTED] wrote: This one's

Issue 571 in lilypond: Odd spacing with grace notes below the staff

Issue 571: Odd spacing with grace notes below the staff http://code.google.com/p/lilypond/issues/detail?id=571 New issue report by v.villenave: % Please also read Andrew's full report on % http://lists.gnu.org/archive/html/bug-lilypond/2008-02/msg4.html \version 2.11.38 \paper {

Re: Hairpin and Textscript

Trevor Daniels wrote: ... http://kainhofer.com/~lilypond/Documentation/user/lilypond-learning/index.html which shows a bug! The ottava bracket isn't moved no matter what value you specify, at least when I try with the latest 2.11.38 code from GIT. Unfortunately, this means that the

Re: Bug: score-final mark mangles score-final tuplet bracket

On 05/02/2008, Trevor Bača [EMAIL PROTECTED] wrote: Could you please consider this one for the tracker? It's quite specific thing ever, but highly reproducible (and quite irritating). Hi Trevor, 5 insane settings and you're complaining that the output is weird? Honestly, you're pushing it

Re: Bug: instrumentName is not being vertically centered when using template 'piano centered dynamics'

On 04/02/2008, Graham Percival [EMAIL PROTECTED] wrote: You hear that, Valentin? Be ambitious. :) Well, I am, but generally you're the one who prevents me from being so :) Honestly, I think this is all about LilyPond dumb-but-logical way of doing things, so the current behavior doesn't seem

Issue 572 in lilypond: Feature request: vertical instrumentName alignment should ignore non-stafflike contexts

Issue 572: Feature request: vertical instrumentName alignment should ignore non-stafflike contexts http://code.google.com/p/lilypond/issues/detail?id=572 New issue report by v.villenave: % It would be nice if the instrumentName for more than % one staff were vertically centered before the

RE: Hairpin and Textscript

Thanks Mats. Actually the bug is in the manual :( The ottava spanner is created in the Staff context, but I omitted to specify the context in the \override in the example. \once \override Staff.OttavaBracket #'outside-staff-priority = #340 works fine (at least in 2.11.34) Trevor D

Issue 467 in lilypond: Two calls to set-octavation confound intervening clef change

Issue 467: Two calls to set-octavation confound intervening clef change http://code.google.com/p/lilypond/issues/detail?id=467 Comment #9 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are

Re: set associatedVoice and disappearing lyrics

Valentin Villenave wrote: On 05/02/2008, Mats Bengtsson [EMAIL PROTECTED] wrote: Well, the root of the problem is the fact that you have to specify the voice change one note ahead, which is inconvenient in itself. Indeed. Since a bug fix isn't likely to happen very soon, a

Re: set associatedVoice and disappearing lyrics

On 05/02/2008, Mats Bengtsson [EMAIL PROTECTED] wrote: Well, the root of the problem is the fact that you have to specify the voice change one note ahead, which is inconvenient in itself. Indeed. Since a bug fix isn't likely to happen very soon, a first step would be to add a note in the

Issue 542 in lilypond: bus error ancient music 2.11.36

Issue 542: bus error ancient music 2.11.36 http://code.google.com/p/lilypond/issues/detail?id=542 Comment #3 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC

Issue 558 in lilypond: Spanner 'Hairpin' error when a MultiMeasureRest occurs after a line break

Issue 558: Spanner 'Hairpin' error when a MultiMeasureRest occurs after a line break http://code.google.com/p/lilypond/issues/detail?id=558 Comment #3 by v.villenave: Has this commit already been implemented? It works fine with .38 here... Issue attribute updates: Status: Verified --

Issue 563 in lilypond: rename: \fatText - \textLengthOn

Issue 563: rename: \fatText - \textLengthOn http://code.google.com/p/lilypond/issues/detail?id=563 Comment #6 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC

Issue 562 in lilypond: Vertical spacing: wrong extent-estimate with StaffGroups and hara-kiri

Issue 562: Vertical spacing: wrong extent-estimate with StaffGroups and hara-kiri http://code.google.com/p/lilypond/issues/detail?id=562 Comment #5 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because

Issue 552 in lilypond: Metronome mark affects spacing

Issue 552: Metronome mark affects spacing http://code.google.com/p/lilypond/issues/detail?id=552 Comment #3 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields

Issue 528 in lilypond: wish: underline markup

Issue 528: wish: underline markup http://code.google.com/p/lilypond/issues/detail?id=528 Comment #7 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this

Issue 336 in lilypond: octavation, change clef produces incorrect note positions

Issue 336: octavation, change clef produces incorrect note positions http://code.google.com/p/lilypond/issues/detail?id=336 Comment #5 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Labels: fixed_2_11_38 -- You received this message because you are

Re: set associatedVoice and disappearing lyrics

On Tue, 05 Feb 2008 13:33:42 +0100 Mats Bengtsson [EMAIL PROTECTED] wrote: Since a bug fix isn't likely to happen very soon, a first step would be to add a note in the documentation. I offer to do that if you wish. This is in vocal.itely? Yes please. Cheers, - Graham

Re: Issue 569 in lilypond: Consistency in property names: beam-thickness

On the other hand, if we do this change, then we loose the consistency with all other objects, where the property name thickness is used to denote the thickness. In my opinion, we would get even more consistency if we renamed beam-thickness to thickness also for StemTremolo objects (even though,

Issue 509 in lilypond: collision nested tuplet numbers

Issue 509: collision nested tuplet numbers http://code.google.com/p/lilypond/issues/detail?id=509 Comment #1 by tdanielsmusic: There is no collision if the tuplet notes are lower on the staff so the stems and tuplet brackets are placed above the notes, but the collision still exists for high

Error is cross-bar arpeggios using times

I'm not top posting. Hi All, For a piece of piano music, I wrote a part with 2-hand arpeggios in \times 8/7. It was originally written with LilyPond 2.6.? where the output looked ok, but with v. 2.10.25, the --- 7 --- signs (dunno how they're called in English :-/) get printed in the wrong