![[icon]](../../../../Documentation/pictures/out-www/lelie-icon.png){kind=icon}
GNU LilyPond
Welcome to the home of the GNU Music Typesetter
| What is LilyPond |
|
General information Simple examples Complex examples |
| Download |
|
GNU/Linux binaries Windows Source code |
| Documentation |
|
Tutorial Manual Glossary other ... |
| Support |
|
Mailing lists Search WikiWiki FAQs |
| External sites |
|
lilypond.org/development lilypond.org/stable ftp.lilypond.org Mutopia Other music online |
Node:Scheme output, Next:ASCIIScript output, Previous:PostScript output, Up:Output formats
Scheme output
In the typesetting stage, LilyPond builds a page description, which is
then written to disk in postscript, TeX or ASCII art. Before it is
written, the page description is represented as Scheme expressions. You
can also dump these Scheme expressions to a file, which may be
convenient for debugging output routines. This is done with the Scheme
output format
$ lilypond -fscm foo.ly GNU LilyPond 1.3.144 Now processing: `foo.ly' Parsing... Interpreting music...[3] Preprocessing elements... Calculating column positions... paper output to foo.scm... $ head -4 foo.scm ;;; Usage: guile -s x.scm > x.tex (primitive-load-path 'standalone.scm) ; (scm-tex-output) (scm-ps-output) $ guile -s foo.scm > foo.tex
Please send GNU LilyPond questions and comments to lilypond-user@gnu.org.
Please send comments on these web pages to lilypond@packages.debian.org
Copyright (c) 1997--2001 Han-Wen Nienhuys and Jan Nieuwenhuizen.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.