bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Defect [new]: \partcombine: accidental reminders of first partlost.


From: Phil Holmes
Subject: Re: Defect [new]: \partcombine: accidental reminders of first partlost.
Date: Sun, 22 Jan 2012 11:50:30 -0000

"Xavier Scheuer" <address@hidden> wrote in message news:address@hidden
On 19 January 2012 18:06, Peter Häring <address@hidden> wrote:
\partcombine  { bes'1 b'! } { g'1 b' }

%Second example: second part has a reminder natural; it is shown in combined
% parts (as it should be).
\partcombine { d''1 b' } { bes'1 b'! }

Workaround:

 \partcombine  { bes'1 \partcombineApartOnce b'! } { g'1 b' }

 \partcombine { d''1 b' } { bes'1 \partcombineApartOnce b'! }

but then we fall in the case of displaying "complex chords", like
<bes! b> .  I thought we had this accidentals in "complex chords" as an
issue on the tracker but I do not find it.  It as been discussed several
times on various LilyPond mailing lists, there is a snippet "Displaying
complex chords" on the LSR: http://lsr.dsi.unimi.it/LSR/Item?id=505
(not always "usable").

AFAIK developers would like examples of how such situations are handled
by music publishers.  Do they use separate note heads, where do they
place the accidentals, etc.  But if "complex accidentals in chords" is
not tracked yet, then it should be added IMHO.
Relevant code showing the issue is simply

 <bes b>

If someone could have a look at what Ross, Read or Gould say about this,
how to engrave it, that would be very kind.

I do not know how (forced, cautionary) accidentals are handled by
\partcombine but that may require a separate issue.

Cheers,
Xavier

--
Xavier Scheuer <address@hidden>

Marek added this as http://code.google.com/p/lilypond/issues/detail?id=2235


--
Phil Holmes
Bug Squad






reply via email to

[Prev in Thread] Current Thread [Next in Thread]