release: 1.1.36

[lilypond.git] / Documentation / faq.yo

diff --git a/Documentation/faq.yo b/Documentation/faq.yo
index ea2e567fe0c430947c2246e0aa61bdeb7626657d..aa15a3196ea6fc19b224066704f75df11beb4c05 100644 (file)
--- a/Documentation/faq.yo
+++ b/Documentation/faq.yo
@@ -391,24 +391,28 @@ previous fonts, including the file(.pk) and file(.tfm) fonts in
 file(/var/lib/texmf).  A script automating this has been included, see
 file(buildscripts/clean-fonts.sh).
 
-
 question(How does PS output work?)
 
 itemize(
-it() Generate the PostScript Type-3 fonts.  In the file(mf/) 
+ it()
+Generate the PostScript Type-3 fonts. In the file(mf/) 
 subdirectory, issue:
 verb(
-    make pfa
-)
-it() Run lilypond with option tt(-f ps):
+       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 pfas. In the source tree, this is file(mf/out/),
+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 &
 )
 )
@@ -416,7 +420,7 @@ verb(
 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