[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Treating a tie as a slur
From: |
Valentin Villenave |
Subject: |
Re: Treating a tie as a slur |
Date: |
Sun, 14 Nov 2010 12:55:55 +0100 |
On Sun, Nov 14, 2010 at 12:38 PM, David Kastrup <address@hidden> wrote:
> Means a tie, as indicated by the user.
Oh. So, setting tieWaitForNote would disable the "automatic-slurs" feature?
> Means bad input. Configurable to be treated as a slur to b.
Then it would no longer be "bad input", would it?
I was about to say that setting or unsetting properties shouldn't
affect what is considered "bad" or "good" input syntax... But setting
such things ignoreMelismata already affects the input quite a lot.
My main concern is that such a change would amount to make the input
syntax more "fault-tolerant", which isn't the direction we've been
taking so far.
That being said, unterminated ties are currently allowed and do not
produce any warning, so I don't think the current situation is optimal
either. If anything, we could at least output a "warning: unfinished
tie. A slur will be printed instead".
How does it seems to you?
Cheers,
Valentin.
- Treating a tie as a slur, Johan Vromans, 2010/11/11
- Re: Treating a tie as a slur, Valentin Villenave, 2010/11/11
- Re: Treating a tie as a slur, Johan Vromans, 2010/11/12
- Re: Treating a tie as a slur, Valentin Villenave, 2010/11/12
- Re: Treating a tie as a slur, David Kastrup, 2010/11/13
- Re: Treating a tie as a slur, Carlo Stemberger, 2010/11/14
- Re: Treating a tie as a slur, Valentin Villenave, 2010/11/14
- Re: Treating a tie as a slur, David Kastrup, 2010/11/14
- Re: Treating a tie as a slur,
Valentin Villenave <=
- Re: Treating a tie as a slur, David Kastrup, 2010/11/14
- Re: Treating a tie as a slur, Jan Warchoł, 2010/11/14
- Re: Treating a tie as a slur, Johan Vromans, 2010/11/14
- Re: Treating a tie as a slur, Trevor Daniels, 2010/11/14
- Re: Treating a tie as a slur, Valentin Villenave, 2010/11/14