[Top][All Lists]

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

Re: Accidentals tied over a system break

From: Urs Liska
Subject: Re: Accidentals tied over a system break
Date: Thu, 08 Oct 2015 20:13:50 +0200
User-agent: K-9 Mail for Android

Am 8. Oktober 2015 19:59:57 MESZ, schrieb Sven <address@hidden>:
>Sorry, I didn't know this is a known issue.
>And thanks for correcting me on how to actually remove the second
>Urs: \once \omit Accidental get's rid of the bugger, while \once \hide
>Accidental makes it transparent, leaving its space in tact.

Well, it's "correct", but still it is a hack. Maybe you inferred it from he 
discussion: you get rid of the redindant accidental - but if your line breaking 
should ever cjange it won't automatically come back.

>2015-10-08 19:14 GMT+02:00 David Kastrup <address@hidden>:
>> Simon Albrecht <address@hidden> writes:
>> > On 08.10.2015 16:38, Trevor Daniels wrote:
>> >> Furthermore, if the tie is removed the sharp on the final fis
>> >> is also removed.  The issue is, without the \break the final fis
>> >> needs the sharp as the second fis doesn't have one, being tied
>> >> to the first fis.  Adding the \break causes the second fis to
>> >> need (and get) a sharp, but the sharp on the third fis, which is
>> >> now redundant, is not removed.  Seems to be a bug to me.
>> >
>> > And, just as David said, one that is long known and being tracked:
>> > <http://sourceforge.net/p/testlilyissues/issues/649/>. There has
>> > some discussion, but at any rate it’s nonsense to have both
>> > accidentals, and IMO the second should be left out.
>> I don't think there's much of a disagreement on that.  It's just that
>> it's quite tricky to do.  The "remove tied accidental unless after
>> break" is somewhat easy to do: the accidental in its final phase of
>> typesetting checks whether there is a tie leading to it and whether
>> tie is just a broken-off part of a tie.  If it is, the accidental is
>> killed.
>> However, keeping track of the complex relation between this kind of
>> line-break related killed accidental and the following one is rather
>> harder to pin down since the following one needs to have no vicinity
>> either tie or line break.
>> --
>> David Kastrup
>lilypond-user mailing list

Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

reply via email to

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