Re: Accidental placement in voiceTwo vs. another staff

2013-06-28 Thread Eluze
in the upper voice. Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Accidental-placement-in-voiceTwo-vs-another-staff-tp147446p147488.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mail

Re: Accidental placement in voiceTwo vs. another staff

2013-06-28 Thread James Harkins
> the accidental is repeated because we are in a new measure and the natural > sign avoids the accidental of the top voice. > > when the notes are tied the accidental is not repeated but it seems like > LilyPond still reserves some space for it. > > I tried to set the Accidental stencil to false

Re: Accidental placement in voiceTwo vs. another staff

2013-06-27 Thread Eluze
look good. that's what I mean with "where necessary" - of course the best would be to fix the bug and return to automagic engraving Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Accidental-placement-in-voiceTwo-vs-another-staff-tp14744

Re: Accidental placement in voiceTwo vs. another staff

2013-06-27 Thread David Kastrup
Eluze writes: > the only workaround I could find is to tweak manually where necessary: > > \tweak Accidental #'extra-offset #'(1 . 0) b If a line break occurs at the bar-line, this will not look good. -- David Kastrup ___ lilypond-user mailing lis

Re: Accidental placement in voiceTwo vs. another staff

2013-06-27 Thread Eluze
are tied the accidental is not repeated but it seems like >> LilyPond still reserves some space for it. > > precisely. > > And yes, i think this is exactly issue 3106. the only workaround I could find is to tweak manually where necessary: \tweak Accidental #'extra-offset #

Re: Accidental placement in voiceTwo vs. another staff

2013-06-27 Thread Janek WarchoĊ‚
Hi, 2013/6/27 Eluze : > James Harkins-2 wrote >> Is this a known bug? >> >> It looks like LP is trying to avoid a collision between the natural sign >> in the top staff's voiceTwo and the sharp sign in the bottom staff. But of >> course they are nowhere near touching, so there should be no need fo

Re: Accidental placement in voiceTwo vs. another staff

2013-06-27 Thread Eluze
; Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Accidental-placement-in-voiceTwo-vs-another-staff-tp147446p147447.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Accidental placement in voiceTwo vs. another staff

2013-06-26 Thread James Harkins
Is this a known bug? It looks like LP is trying to avoid a collision between the natural sign in the top staff's voiceTwo and the sharp sign in the bottom staff. But of course they are nowhere near touching, so there should be no need for collision avoidance. (Sorry I'm on a slightly older stab