bug-lilypond
[Top][All Lists]
Advanced

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

Re: "repeat" slashes and the nature of lilypond


From: Hans Forbrich
Subject: Re: "repeat" slashes and the nature of lilypond
Date: Mon, 21 Feb 2005 07:51:28 -0600
User-agent: KMail/1.7.1

On February 20, 2005 09:07 pm, address@hidden wrote:
> > I can see that one chord symbol could be interpreted in a variety of
> > different voicings/inversions/etc. But it is still written with one
> > indication/symbol.
>
> With conventions that differ widely; hence lilypond enforcing one
> system I see as inelegant.

Responding as a very satisfied long time North American user of Lilypond and 
as a reader of this thread:

Elegant or not,  this is a system that has been made available and it is 
workable.  Unless I misinterpret, you are asking to have the system usurped 
or thrown out due to it's [multiple choice:] {in-elegance, inflexibility, not 
conforming to lack of standardization}.  

Your assertion of "Lilypond forcing certain conventions onto the musician that 
should not be enforced" may be true, but without some convention the result 
degenerates to something poorly supported that is used by few, or even just 
one, individuals.    Since I am comfortable with the existing system, even if 
it may be inelegant (an assertion I do not agree with) I would hope your 
proposal allows the existing system to be kept and offers an alternative.  
Otherwise it simply changes from something acceptable to me to something 
acceptable to you - can you say religion.

You have been using rather dark language [be wary of anyone who has a degree 
in jazz; anesthetically (and practically) erroneous; take issue with that 
too; many other examples], presumably in an attempt to sway the developers 
through negative assertion.   Not to disparage the offer but to provide some 
other perspective, your $50 offer amount to 1-2 hours of effort by an 
independent commercial programmer.   Since this discussion has probably used 
up more than an hour of developer time, and since Han-Wen usually delivers 
the quick ones in very short order without much discussion, this suggests 
some other (positive assertion) mechanisms to get the appropriate community 
on your side.

Your cause would be considerably furthered if you would come up with the 
comprehensive user documentation, in the context of Lilypond as compared to 
the others.

cheers
/Hans
-- 
Proud user of Lilypond Music Typesetter
http://www.lilypond.org




reply via email to

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