is not a recommendation, however. We recommend you use Unix, in
particular, use GNU/Linux. For further information see file(README-W32).
+question(Where is guile-config)
+
+RedHat RPMS don't include guile-config. You need guile-config as it
+was produced during the RPM build run. Build the RPM from source
+(file(.src.rpm)), and use the guile-config that is in
+file(/usr/src/redhat/BUILD/guile-1.3/guile-config/).
+
+
question(I get all kinds of errors while compiling file(parser.cc))
LilyPond uses features of bison version 1.25. Please confirm that
question(Do you support multiple staff-sizes?)
-Yes and no. At this time you can choose between 11, 13, 16, 19,
-20, 23 and 20 pt staff-size. The sizes can't be changed per staff
-(yet). Look at file(standchen.ly) for an example.
-
+Yes. At this time you can choose between 11, 13, 16, 19, 20, 23 and
+20 pt staff-size. Use the staffLineLeading property for setting the
+size of the staff, and fontSize for setting the size of the glyphs.
question(Do you support Gregorian chant notation?)
No. There is no reason why LilyPond can't be extended to do so, but
we haven't done it yet (and there are currently no plans to do it).
+question(Do you support grace notes?)
+
+No. But they can kludged. See file(input/test/grace.ly)
+
sect(How do I ....)
question(How do I get bar numbers?)
-See file(init/engraver.ly). You have to uncomment some entries. To
-do this `portably' you should redefine some engravers in your own
-source files. Check out file(init/rhythm.ly).
+See file(input/test/bar-scripts.ly).
sect(Development)
question(Why do I need g++ >= 2.8 / EGCS-1.1 ?)
-Supporting more compilers then EGCS/G++ 2.8 is unlikely to make
+Supporting more compilers than EGCS/G++ 2.8 is unlikely to make
LilyPond run on more platforms. It would give us an enormous headache
in detecting and catering for every variant of every compiler: not
having to support other compilers saves us a em(lot) of trouble.
file(/var/lib/texmf). A script automating this has been included, see
file(buildscripts/clean-fonts.sh).
+question(all the pk and tfm
+fonts are created in the directory where the mudela file is, not in
+"/var/spool/texmf" where I think they should be.)
+
+Mats Bengtsson <mats.bengtsson@s3.kth.se> writes:
+
+The simple solution used by Anthony Fok in the Debian distribution of
+Lilypond is to link the mf/ directory to
+/usr/lib/texmf/fonts/source/public/lilypond Depending on what
+distribution of teTeX and Linux you have installed, there might also
+be other places like /usr/local/lib/texmf/fonts/source/public/lilypond
+or /var/spool/texmf//fonts/source/public/lilypond
+
+Wherever you put it, don't forget to run mktexlsr (or texhash for
+older installations) afterwards, so that TeX will find the files.
+Also, don't forget to remove all old .tfm and .*pk files when the font
+is updated (as it will be in version 1.1.40, for example).
+
+question(How does PS output work?)
+
+itemize(
+ it()
+Generate the PostScript Type-3 fonts. In the file(mf/)
+subdirectory, issue:
+verb(
+ make pfa
+) in the mf/ subdirectory. This will also make file(mfplain) for metapost.
+it()
+Run lilypond with option tt(-f ps):
+verb(
+ lilypond -fps foo.ly
+)
+it() To view the file(.ps) output with GhostView, set GS_FONTPATH to the
+directory containing the file(pfa)s, and set GS_LIB to the directory containing the file(.ps) library files of LilyPond. In the source tree, these are file(mf/out/) and file(ps/).
+
+
+i.e. do something like:
+verb(
+ export GS_FONTPATH=$HOME/usr/src/lilypond/mf/out
+ export GS_LIB=$HOME/usr/src/lilypond/ps
+ gv foo.ps &
+)
+)
+
+Direct PS output is still experimental. For creating nice looking ps
+output, use TeX() and code(dvips).
+
question(The beams and slurs are gone if use the XDvi magnifying glass!?)
The beams and slurs are done in PostScript. XDvi doesn't show
projects / lilypond.git / blobdiff