the automated method with @command{lilypond-book}.
@menu
-* Many quotes from a large score::
-* Inserting LilyPond output into OpenOffice and LibreOffice::
-* Inserting LilyPond output into other programs::
+* LuaTex::
+* OpenOffice and LibreOffice::
+* Other programs::
@end menu
-@node Many quotes from a large score
-@unnumberedsubsec Many quotes from a large score
-If you need to quote many fragments from a large score, you can also use
-the clip systems feature, see @ruser{Extracting fragments of music}.
+@node LuaTex
+@subsection LuaTex
+
+@cindex LuaTex
+@cindex lyluatex
+
+As well as @code{lilypond-book} to integrate LilyPond output,
+there is an alternative program that can be used when using LuaTex
+called
+@uref{https://github.com/jperon/lyluatex/blob/master/README.en.md,lyluatex}.
-@node Inserting LilyPond output into OpenOffice and LibreOffice
-@unnumberedsubsec Inserting LilyPond output into OpenOffice and
-LibreOffice
+@node OpenOffice and LibreOffice
+@subsection OpenOffice and LibreOffice
@cindex OpenOffice.org
@cindex LibreOffice.org
+@cindex OOoLilyPond
LilyPond notation can be added to OpenOffice.org and LibreOffice with
@uref{http://@/ooolilypond@/.sourceforge@/.net@/,OOoLilyPond}, an
it appears to still work with version 4.
-@node Inserting LilyPond output into other programs
-@unnumberedsubsec Inserting LilyPond output into other programs
+@node Other programs
+@subsection Other programs
-To insert LilyPond output in other programs, use @code{lilypond}
-instead of @code{lilypond-book}. Each example must be created
-individually and added to the document; consult the documentation for
-that program. Most programs will be able to insert LilyPond output in
-@file{PNG}, @file{EPS}, or @file{PDF} formats.
+Other programs that can handle @file{PNG}, @file{EPS}, or @file{PDF}
+formats should use @code{lilypond} instead of @code{lilypond-book}.
+Each LilyPond output file must be created and inserted separately.
+Consult the program's own documentation on how to insert files from
+other sources.
-To reduce the white space around your LilyPond score, use the following
-options;
+To help reduce the white space around your LilyPond score, use the
+following options;
@example
\paper@{
scoreTitleMarkup = ##f
@}
-@{ c1 @}
+@var{@dots{} music @dots{}}
@end example
-To produce useful image files:
+@noindent
+To produce @file{EPS} images;
@example
-EPS
-
lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts myfile.ly
+@end example
-PNG
+@noindent
+To produce @file{PNG} images;
+@example
lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png myfile.ly
+@end example
-A transparent PNG
+@noindent
+For transparent @file{PNG} images
-lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts \
- -dpixmap-format=pngalpha --png myfile.ly
-@end example
+@smallexample
+lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts -dpixmap-format=pngalpha --png myfile.ly
+@end smallexample
+
+@cindex fragments, music
+@cindex quoting, music fragments
+@cindex music fragments, quoting
+
+If you need to quote many fragments from a large score, you can also use
+the clip systems feature, see @ruser{Extracting fragments of music}.
@node Independent includes
@section Independent @code{include}s
-Some people have written large (and useful!) code that can be
-shared between projects. This code might eventually make its way
-into LilyPond itself, but until that happens, you must download
-and @code{\include} them manually.
+Some users have produced files that can be @code{\include}d with
+LilyPond to produce certain effects and those listed below are part of
+the LilyPond distribution. Also see @ruser{Working with input files}.
@menu
* MIDI articulation::
@node MIDI articulation
@subsection MIDI articulation
-LilyPond can be used to produce MIDI output, for
-@qq{proof-hearing} what has been written. However, only dynamics,
-explicit tempo markings, and the notes and durations themselves
-are produced in the output.
-
-The @emph{articulate} project is one attempt to get more of the
-information in the score into MIDI. It works by shortening
-notes not under slurs, to @q{articulate} the notes. The amount of
-shortening depends on any articulation markings attached to a
-note: staccato halves the note value, tenuto gives a note its full
-duration, and so on. The script also realises trills and turns,
-and could be extended to expand other ornaments such as mordents.
-
-@example
-@uref{http://@/www@/.nicta@/.com@/.au/@/people/@/chubbp/@/articulate}
-@end example
-
-@knownissues
-Its main limitation is that it can only affect things it knows
-about: anything that is merely textual markup (instead of a note
-property) is still ignored.
+@cindex MIDI
+@cindex Articulate project
+
+The @uref{http://www.nicta.com.au/articulate,Articulate} project is an
+attempt to enhance LilyPond's MIDI output and works by adjusting note
+lengths (that are not under slurs) according to the articulation
+markings attached to them. For example, a @q{staccato} halves the note
+value, @q{tenuto} gives a note its full duration and so on. See
+@ruser{Enhancing MIDI output}.
projects / lilypond.git / blobdiff