lilypond-devel
[Top][All Lists]
Advanced

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

Re: Added transition lines for lyrics (issue 565750043 by address@hidden


From: David Kastrup
Subject: Re: Added transition lines for lyrics (issue 565750043 by address@hidden)
Date: Tue, 10 Mar 2020 10:33:37 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Han-Wen Nienhuys <address@hidden> writes:

> On Tue, Mar 10, 2020 at 1:41 AM Dan Eble <address@hidden> wrote:
>>
>> On Mar 9, 2020, at 04:42, Han-Wen Nienhuys <address@hidden> wrote:
>> >
>> > On Mon, Mar 9, 2020 at 12:44 AM Dan Eble <address@hidden> wrote:
>> >> I agree that lots of duplication is something that should be
>> >> avoided, but so is the conflation of style and meaning.  A lyric
>> >> hyphen separates syllables; this arrow thing means something
>> >> more.
>> >
>> > Can you have a hyphen and a transition between two syllables at the
>> > same time? If not, that suggests that they are two variations of
>> > essentially the same thing.
>>
>> I would agree that a hyphen and a "transition line" are mutually
>> exclusive ways of demarcating syllables; but that doesn't make a
>> "transition line" a kind of hyphen any more than it makes a staccato
>> mark a kind of legato mark or blue a kind of red.
>
> In LilyPond All articulation marks (staccato, portato, staccatissimo)
> are Script grobs, and they use identical code, both in the engravers
> and the grob formatting.

Which can end up a nuisance if you want to change some, but not all.

> I never said that blue is a kind of red. I said "two variations of
> essentially the same thing." Blue and red are both colors, so they
> could be implemented in terms of a generic 'color' type.
>
> From a music-semantical perspective, hyphens and transitions may be
> quite different, but from the typographical perspective, they really
> seem quite similar, which means that they can share a lot of code, up
> to and including the Grob name and the engraver instance producing
> them.

It's worth noting that sharing the engraver does not necessitate sharing
the Grob name (and respective defaults): different grobs can share an
interface, and it is interfaces that an engraver triggers on with regard
to the typesetting.  In a similar vein, engravers react to event
classes rather than event types.

So code sharing does not necessitate item sharing.

-- 
David Kastrup



reply via email to

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