* Custodes::
* Tuning output::
* Page layout::
+* Output formats::
* Sound::
* Music entry::
* Skipping corrected music::
* Tuning per grob ::
* What to tune?::
* Font selection::
-* Text markup::
-* Embedded @TeX{}::
+* Text markup::
+* Invisible grobs::
+* Embedded TeX::
@end menu
@node Tuning groups of grobs
@subsection Invisible grobs
@cindex invisible grobs
-A grob can be made invisible in a number of ways:
+You can imagine a number of situtations where you would want to make
+certain grobs not show up in the output. There may be aesthetic
+reasons, to make the output resemble an (old) manuscript as close as
+possible, or to make lessons or exercises for students.
+
+Grobs can be made invisible in a number of ways:
@ignore
FIXME
Show visibility-lambda and explain why it doesn't work for eg
StaffSymbol
-
@end ignore
+Here's an example with blanked-out notes and stems:
+@lilypond[singleline,verbatim]
+blanknotes = {
+ \property Voice.NoteHead \override
+ #'molecule-callback = #(lambda (x) '())
+ \property Voice.Stem \override
+ #'molecule-callback = #(lambda (x) '()) }
+
+unblanknotes = {
+ \property Voice.NoteHead \revert #'molecule-callback
+ \property Voice.Stem \revert #'molecule-callback }
+
+\score {
+ \notes\relative c'' {
+ \time 6/4;
+ a b c b \blanknotes c \unblanknotes d
+ }
+}
+@end lilypond
Some grobs require a special treatment.
-Make staff invisible:
-@lilypond[singleline,verbatim}
+Rhythm exercise: make staff invisible and squash pitches:
+@lilypond[singleline,verbatim]
\score {
- \notes { c4 c4 c8 c8 }
+ \notes { \time 3/4; c4 c c8 c | c4 c c8 c }
\paper {
\translator {
\StaffContext
}
@end lilypond
-Make bar lines invisible:
-@lilypond[singleline,verbatim}
+Some modern music does not show bar lines:
+@lilypond[singleline,verbatim]
\score {
\notes \relative c'' {
a b c d
}
}
}
-
-
@end lilypond
-@node Embedded @TeX{}
-@subsection Embeded @TeX{}
+
+@node Embedded TeX
+@subsection Embeded TeX
@cindex embedded tex
@cindex embedded tex
LilyPond can output processed music in different output formats.
-@node @TeX{} output
-@section @TeX{} output
-@cindex @TeX{} output
+@menu
+* TeX output::
+* PostScript output::
+* Scheme output::
+* ASCIIScript output::
+@end menu
+
+@node TeX output
+@subsection TeX output
+@cindex TeX output
LilyPond will use @TeX{} by default. Even if you want to produce
PostScript output for viewing or printing, you should normally have
@node PostScript output
-@section PostScript output
+@subsection PostScript output
@cindex PostScript output
@cindex direct PostScript output
LilyPond can produce PostScript directly, without going through @TeX{}.
-Direct PostScript output has some problems, though.
+Currently, this is mainly useful if you cannot use TeX, because direct
+PostScript output has some problems; see Bugs below.
@example
$ lilypond -fps foo.ly
Preprocessing elements...
Calculating column positions...
paper output to foo.ps...
+
$ cat /usr/share/lilypond/pfa/feta20.pfa foo.ps | lpr
@end example
@node Scheme output
-@section Scheme output
+@subsection Scheme output
@cindex Scheme output
[TODO]
@end example
-@node AsciiScript output
-@section AsciiScript output
-@cindex AsciiScript output
+@node ASCIIScript output
+@subsection ASCIIScript output
+@cindex ASCIIScript output
@cindex ascii script
@cindex ascii art
-LilyPond can output Ascii Art. This is a two step process, LilyPond
-produces an ascii description file, dubbed AsciiScript (extension
-@file{.as}). AsciiScript has a small and simple command set that
+LilyPond can output ASCII Art. This is a two step process, LilyPond
+produces an ASCII description file, dubbed ASCIIScript (extension
+@file{.as}). ASCIIScript has a small and simple command set that
includes font selection, character and string printing and line drawing
commands. The program @file{as2text} is used to translate an .as file
to text.
-To produce ascii art, you must include an ascii art paper definition
+To produce ASCII Art, you must include an ASCII Art paper definition
file in your .ly, one of:
@example
\include "paper-as5.ly"
\include "paper-as9.ly"
@end example
-Here's an example use for Ascii Art output (the example file
+Here's an example use for ASCII Art output (the example file
@file{as-email.ly} is included in the LilyPond distribution), the staff
symbol has been made invisible:
@refbugs
-The ascii art fonts are far from complete and not very well designed.
+The ASCII Art fonts are far from complete and not very well designed.
+It's easy to change the glyphs, though; if you think you can do better,
+have a look at @file{mf/*.af}.
+
Lots of resizable symbols such as slurs, ties, tuplets are missing.
+The poor looks of most ASCII Art output and its limited general
+usefulness make that ASCII Art output has a low priority; it may be
+dropped in future versions.
@c . {Sound}
@node Sound