=head1 DESCRIPTION
-Some questions that have been answered before.
+Some questions that have been answered before. (note: relative paths
+are meant to be relative to the source directory)
=head2 Installing
A: [This only applies if you don't do C<make install>, and develop out
of the source directory]
-
+I have a directory which contains all music related stuff,
+
~/something/
which contains:
lilypond/ # the directory as unpacked from the tarball
releases/ # directory for .tar.gz releases
patches/ # directory for patches between different releases
- test/
+ test/ # create tarballs and do diffs from this directory
~/something/lilypond/bin is in the PATH, and contains symlinks to the
-compiled executables.
+compiled executables. For some of the scripts to work, you have to set
+
+ LILYPOND_SOURCEDIR=/home/myself/something/lilypond
+
+in the environment.
If you don't use patches, you'd probably want to symlink
good idea, please let us know.
Be warned we will I<not> allow you to leave out the C<#> if the note
-already has an accidental. We won't allow
+already has an accidental, or if the key has a C-sharp. We won't allow
c# c % no way!
a()a()a
-Q: How do I place lyrics under I<each> of the staves in a score, as in
-choral music. I can work out how to put lyrics for each line all under
-the top line, or at the bottom but not between!
-
-A: You change the order lyrics and staves. You have to name all
-staves (lyric and melodic), otherwise they will end up in the same
-staff/lyricline
-
-
- \score {
- < \melodic \type Staff = "treble" \trebleMelody
- \lyric \type Lyrics = "tlyrics" \trebtext
- \type Staff = "bass" \melodic \bassMelody
- \lyric \type Lyrics = "blyrics" \basstext
- >
- \paper { }
- }
-
-
-
Q: I want to insert some TeX commands
output PostScript or render to an X window too), so using TeX will
make sources non-portable at some time.
-=head2 Miscellaneous
+=head2 Do you support ...
Q: Do you support pop songs (chords, single staff, lyrics)?
-A: Yes, see the F<twinkle-pop> example
+A: Yes, see the F<twinkle-pop> example.
Q: Do you support guitar chord diagrams?
fine points of this notation. We would welcome anyone who could give
this a try.
-Q: Do you support TAB notation
+Q: Do you support TAB notation?
A: No. The same as for the previous question goes, but TAB is a lot
more work than diagrams (TAB needs modification of Parser, Lexer,
Staff, Notehead, Stem code and all the code that creates these graphic
elements.)
+Q: Do you support multiple staff-sizes?
+
+A: Yes and no. At this time you can choose between 16 or 20 pt
+staff-size (you can have other sizes, but you need to tinker with the
+fonts to get those). The sizes can't be changed per staff (yet).
+Look at F<standchen.ly> for an example.
+
+
+=head2 How do I ....
+
Q: How do I change the TeX layout?
A: See F<lilyponddefs.tex>, it has some comments.
+Q: How do I place lyrics under I<each> of the staves in a score, as in
+choral music. I can work out how to put lyrics for each line all under
+the top line, or at the bottom but not between!
+
+A: You change the order lyrics and staves. You have to name all
+staves (lyric and melodic), otherwise they will end up in the same
+staff/lyricline
+
+
+ \score {
+ < \melodic \type Staff = "treble" \trebleMelody
+ \lyric \type Lyrics = "tlyrics" \trebtext
+ \type Staff = "bass" \melodic \bassMelody
+ \lyric \type Lyrics = "blyrics" \basstext
+ >
+ \paper { }
+ }
+
+
+Q: How do I put more than one marking on a note.
+
+A: You can stack them
+
+ c4^"a"^"b"
+
+or use spacing-notes to put markings at different horizontal positions
+
+ < c1
+ { s4\ff s4^"text" s4-\marcato s4 }
+ >
+
=head2 Development
"fait accompli", ie., to send me a patch.
+Q: I made some code, how do I get you to include it?
+
+A: Send in a patch:
+
+ diff -urN old-file new-file > patch
+
+or
+
+ diff -urN old-directory/ new-directory/ > patch
+
+Alternatively, you can use bin/make-patch.py
Q: How do I learn the C++ code?
=head2 Running
-Q: I don't get midi-output, even if I use B<-M>
+Q: There are lots of warning messages for the printing, all
+beginning with:
+
+ dvilj4l: warning: Invalid keyword or value in \special -
+
+A: You should use dvips and ghostscript to print it: the slurs and
+beams are PS C<\special> commands
+
+
+Q: My symbols are all messed up after I upgraded, and I get
+dvi-checksum errors!
+
+A: We mucked with the fonts in the upgrade. Remove I<all> previous
+fonts, including the .pk and .tfm fonts in F</var/lib/texmf>. A
+script automating this has been included, see F<bin/clean-fonts.sh>
+
+Q: I don't get midi-output, even if I use B<-M>!
A: Your \score should include a \midi block, eg.
projects / lilypond.git / commitdiff