A: LilyPond uses features of bison version 1.25. Please confirm that
you are using a version 1.25 or better. Don't forget to do "make
-clean" after installing it
+clean" after installing it. Don't forget to remove the stale
+bison.simple as well.
If the problem persists, then please mail me.
A:
- ~/something
- lilypond # the directory as unpacked from the tarball
- releases # directory for .tar.gz releases
- patches # directory for patches between different releases
+ ~/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/
+
~/something/lilypond/bin is in the PATH, and contains symlinks to the
compiled executables.
+If you don't use patches, you'd probably want to symlink
+
+ lilypond -> lilypond-x.y.z
+
=head2 Language: mudela
Q: Why can't you type C<#c> in stead of C<cis> ?
cis cis
#c #c
+Why, you might ask? Because independently of how it was written, you
+would say that you are playing and reading "two C-sharp" notes.
+
+
+Q: What is C<cis> anyway
+
+A: C<cis> is the dutch naming for C-sharp. The notes are named
+a, b,.., g. The suffix -is means sharp, and -es flat. This system is
+common in a number of languages (such as swedish, dutch, german.)
+Certain other languages (such as English, French and Italian) just add
+the word for "sharp" to the notename.
+
+We chose the Dutch system, because we're dutch. You are free to chose
+whatever names you like; they are user definable.
Q: I can type
a()a()a
-Q: Why shouldn't I put all commands (\clef, \meter) inside the music?
-
-A: You should do what you like, but at some time we will enable
-quoting of music ("Stichnoten"). Besides if you are going to type an
-orchestral score, then you'd probably want to enter most of the meter,
-repeat commands only once.
-
Q: I want to insert some TeX commands
A: You shouldn't: it's against LilyPond philosophy to have typesetting
=head2 Miscellaneous
+Q: Do you support pop songs (chords, single staff, lyrics)?
+
+A: Yes, see the twinkle-pop example
+
+Q: Do you support guitar chord diagrams?
+
+A: No, not yet. We ourselves don't play guitar, and don't know the
+fine points of this notation. We would welcome anyone who could give
+this a try.
+
+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,
+Notehead, Stem, and stem-code. )
+
Q: How do I change the TeX layout?
A: See lilyponddefs.tex, it has some comments.
- p-col.hh
- *request.hh
- - register.hh
+ - engraver.hh
+ - performer.hh
+ - translator.hh
- score-elem.hh
- - input-music.hh
- - linespace.hh
+ - music.hh
+ - music-list.hh
+ - music-iterator.hh
- item.hh
- spanner.hh
- - voice.hh
Q: Why GPL?
A: If it is reasonable, I'll add XXXX to the TODO list. In general
finding a cute syntax (such as YYYY) isn't very hard. The complicated
-issue how to adapt the internals to do XXXX. The parser is really a
+issue how to adapt the internals to do XXXX. The parser is really a
simple front end to the complicated internals.
Q: Why do I need g++ >= 2.7?
A: By using g++, GNU LilyPond is portable to all platforms which support
g++ (there are quite a few). Not having to support other compilers
-saves us a I<lot> of trouble. GNU LilyPond and FlowerLib use:
-
-=over 4
-
-=item *
-
-builtin bool
-
-=item *
-
-64 bit integral type long long
-
-=item *
-
-typeof
-
-=item *
-
-operator <?, operator >?
-
-=item *
-
-the new for-scope
-
-=item *
-
-class Rational (libg++)
-
-=back
+saves us a I<lot> of trouble.
=head2 Running
A.0: Reconsider. Try Linux. It's fun!
-A.1: Currently (patchlevel 27), GNU LilyPond (and flowerLib) compiles, links
-and runs on windhoos-nt, using the cygnus gnu port (release b17.1).
+A.1: Currently (patchlevel 27), GNU LilyPond (and flowerLib) compiles,
+links and runs on Windows-nt, using Cygnus' gnu port (release b17.1).
I (JCN) only had to make a minor workaround for missing library calls.
-Have a look at http://www.cygnus.com/gnu-win32. To make GNU LilyPond type
-C<make $OSTYPE>. (I am not promising to maintain this platform, it is just
-that when having to use doze, i-m sometimes too lazy to reboot.)
+Have a look at http://www.cygnus.com/gnu-win32. To make GNU LilyPond
+type C<make>. (I am not promising to maintain this platform, it is just
+that when forced into doze, i'm sometimes too lazy to reboot.)
A.2: I haven't had time to find a GCC crosscompiler (I<with> g++ and
-libg++, mind you) to DOS/win (in rpm, please :).
+libg++, mind you) to DOS/Windows (in rpm, please :-)
-Q: I-m dozed enough to run the (sometimes bit stale) .exe-s you distribute.
+Q: I just love to blindly run the (sometimes bit stale) .exe's you distribute.
Why do i need cygwin.dll?
-A: It-s all in this cut-n-paste:
+A: It's all in this cut-n-paste:
Minimalist GNU-Win32 Readme
version 0.1.3
projects / lilypond.git / blobdiff