[Top][All Lists]

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

Re: Feature request - extended ties, addendum

From: Yuval Harel
Subject: Re: Feature request - extended ties, addendum
Date: Mon, 21 Feb 2005 01:48:35 +0200
User-agent: Opera M2/7.54 (Win32, build 3865)

On Sun, 20 Feb 2005 21:10:06 +0100, Matevz Jekovec <address@hidden> wrote:

Steve D wrote:

Is there actually a need to integrate the \extendedTies block? IMO,
there should only be a usual ~ tie simbol, which should work until the
first same-pitch note.

That would cause a problem with chords. For example in {<e a>4 ~ <e g> --some-music-- a} the two a's would get tied, which will come quite unexpectedly to the user. I think that practically, partially-tied chords will be lost as a feature.

But I still think that we can get along without an \extendedTies block. I suggest one of the following:

- Support tying individual notes from chords, so the correct way to write the previous example is {<e~ a>4 <e g>}. This is probably the cleanest solution, and maybe the only way to get some strange constructs like {<c~ e> f <c g> e} right - though I don't think I've ever seen something like that.

- Add a new piece of syntax for an extended tie, such as {c ~~ e ~~ g ~ <c e g>} or {c~( e~( g~ <c e g>~). Probably easiest to implement, and IMO still a significant improvement over \extendedTies.

- Make ties starting at chords an exception - these have to match the next notes or else be nulled.
Simple, but I don't like exceptions :)


reply via email to

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