Walter Hofmeister wrote:
I have noticed that over the last year there have been repeated requests
for how to do certain things (height of alternative ending and getting
chords to appear at the correct height). Perhaps much of this could be
solved by having an organized document that is included
Ben Crowell writes:
> In principle, I agree with Joe about users pitching in and
> helping. However, IMO that's not really possible
Helping is easier than you might imagine and it usually is quite
rewarding. It only costs some time and some determination. See
what you can figure out yourself, a
TS Sunhede Fulk wrote:
>PS. I love Lilypond,
So do I!
>but the manual is really awful. You really need to write it with a user/reader who
>has no programming experience in mind.
Joe Neeman wrote:
>I agree, but you can help [snip]
>I think part of the problem is that the people most likely to wri
On 6/16/04 4:10 PM, "Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] writes:
>>
>> PS. I love Lilypond, but the manual is really awful. You really need to
>> write it with a user/reader who has no programming experience in mind.
>
While this might be true for some parts of the m
PS. I love Lilypond, but the manual is really awful. You really need
to write it with a user/reader who has no programming experience in mind.
I agree, but you can help - the files are in Documentation/user/*.itely.
Once my exams tomorrow and saturday are over, I promise to finish that
index st
The original problem you mention (that preLilyPondExample didn't
work) is a bug in version 2.2.0-2.2.2 and will be fixed in 2.2.3.
In the mean time, you can find several examples of workarounds in
the mailing list archives, for example
http://lists.gnu.org/archive/html/lilypond-user/2004-06/msg0007
