On Tuesday, 20 July 1999, "Timothy S. Nelson" writes:
> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.
> Send mail to [EMAIL PROTECTED] for more info.
>
> --656896-901690455-932437803=:1644
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Hi there. I have a question, a bug report, and some suggestions. Th
+ e
> question is, is there a website (or preferably a downloadable document) which
> will teach me about TeX?
What do you want to know, TeX or LaTeX? It's my experience that good
documentation on TeX is only available/usable in print. The TeXBook
by Knuth is a fine book on plain TeX...
> The bug report is that midi2ly seems to convert certain note lengths
> incorrectly. I've attached a copy of one of the MIDI files which seems to
> cause the problem. One problem is that the length for the note in bar 4
> should be "1".
*Should be* or *is* "1"? I see that it should be "1", but my guess is
that the note was played just a bit too short --- I haven't checked the
midi durations.
> Another problem is that it output the key signature as "Ees"
> instead of "ees".
Well, it's a major key, so midi2ly stresses that using the convention
of capitalising major keys. The 'bug' is in lily's dutch notenames.
This will be fixed in pl64.
> The first suggestion is that you have some way of specifying a
> syllable pattern, which can then be applied to all stanzas (verses).
I don't understand this. Have a look at \addlyrics in pl63, is that
what you're looking for.
> Another suggestion: I'm making a psalm book (but this applies
> equally to all making collections of songs); wouldn't it be a good idea to
> allow multiple input files, but produce a single DVI/PS file at the end?
I've added to the faq:
6.4: How do I combine multiple pieces into one document
There are several solutions:
o
ly2dvi foo.ly bar.ly
produces one combined foo.dvi
o make a toplevel .ly file that contains al pieces:
% booklet.ly
\input "piece-1.ly"
\input "piece-2.ly"
\input "piece-3.ly"
o make a hybrid /LilyPond .doc document (see the Documen-
tation/tex directory).
For the first two solutions, you will need to move \header
info in each individual piece from toplevel into the \paper
block.
There are several examples in the mutopia directory.
> It might also be nice if the text "Lily was here" was changed to
> "Created with Lilypond".
And:
6.6: How do I change the tagline 'Lily was here'
In the \header field, add a tagline entry, eg
tagline="Typeset by GNU LilyPond"
to get a bit less frivolous tagging.
> Also, I made a postscript file, and asked for A5 paper, and it didn't
> look at all right in ghostview. I don't know whether this is just me, or
> what. If it looks all right to you, just ignore this last paragraph.
I don't know, never done this.
> Thanks again for a nice useful program :).
Thanks,
Jan.
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien/ | http://www.lilypond.org/
