--- /dev/null
+ISOLANG = nl
+depth = ../..
+SUBDIRS = application general learning notation texidocs
+STEPMAKE_TEMPLATES = documentation
+LOCALSTEPMAKE_TEMPLATES = lilypond ly doc-i18n-root
+
+include $(depth)/make/stepmake.make
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@setfilename lilypond-application.info
+@settitle GNU LilyPond Application usage
+@documentencoding UTF-8
+@documentlanguage en
+@include macros.itexi
+@afourpaper
+@c don't remove this comment.
+@ifnottex
+@node Top
+@top GNU LilyPond --- Application Usage
+
+@untranslated
+
+
+@c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
+@end ifnottex
+@c This produces the unified index
+@finalout
+@titlepage
+@title LilyPond
+@subtitle The music typesetter
+@titlefont{Program usage}
+@author The LilyPond development team
+@quotation
+@end quotation
+@vskip 20pt
+@end titlepage
+@copying
+@quotation
+@end quotation
+@end copying
+@ifnottex
+@quotation
+@end quotation
+@end ifnottex
+@ifnottex
+@c @rlearning{About the documentation}.
+@c index web site
+@c index URL
+@c * Install:: How to install or compile.
+@c * Setup:: Using LilyPond with other programs.
+@c maybe add a "Tasks" or "Specific tasks" or something like
+@c that, after Suggestions -gp
+@menu
+* Running lilypond::
+* Updating files with convert-ly::
+* lilypond-book::
+* Converting from other formats::
+* Working on LilyPond projects::
+* Suggestions for writing files::
+* GNU Free Documentation License::
+* LilyPond index::
+@end menu
+
+@end ifnottex
+@contents
+@c @include application/install.itely
+@c @include application/setup.itely
+@include application/running.itely
+@include application/updating.itely
+@include application/lilypond-book.itely
+@include application/converters.itely
+@include application/working.itely
+@include application/suggestions.itely
+@include fdl.itexi
+@node LilyPond index
+@appendix LilyPond index
+
+@untranslated
+
+
+@bye
+
+@c -- SKELETON FILE --
--- /dev/null
+depth = ../../..
+
+LOCALSTEPMAKE_TEMPLATES = ly
+
+include $(depth)/make/stepmake.make
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c Don't replace quotes with directed quotes.
+@set txicodequoteundirected
+@set txicodequotebacktick
+@c ***** Displaying text *****
+@c We need this since @q{\} doesn't work with makeinfo 4.11 --
+@c say @q{@bs{}} instead.
+@c ***** Displaying images not generated by lilypond-book *****
+@c Current installation setup of Info docs requires that all images are
+@c expected to be found in the `lilypond/' subdirectory. `lilypond-book'
+@c already generates proper @image commands for images of music; these
+@c macro definitions do the same for other images.
+@c ***** Headers *****
+@c ***** Indexing *****
+@c Don't remove the `@c' within the macro definition! See section 19.3,
+@c `Macro Details and Caveats', in the texinfo info file for explanation.
+@c
+@c ***** Macros specific to translated docs *****
+@c ugh, cannot set/define global variable 'translationof' in any way :-(
+@set translationof \TEXT\
+@c ***** Macros specific to the web site *****
+@c keep the space for proper nesting of </p>
+@c not strictly necessary, but it makes things easier for updating news
+@c keep the space for proper nesting of </p>
+@c @image{\IMAGE-FILE\}
+@c @image{\IMAGE-FILE\}
+@c @image{\IMAGE-FILE\}
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Converting from other formats
+@chapter Converting from other formats
+
+@untranslated
+
+
+@c @ref{Setup for MacOS X}.
+@menu
+* Invoking midi2ly::
+* Invoking musicxml2ly::
+* Invoking abc2ly::
+* Invoking etf2ly::
+* Generating LilyPond files::
+@end menu
+
+@node Invoking midi2ly
+@section Invoking @command{midi2ly}
+
+@untranslated
+
+
+@c index MIDI
+@c ommand{midi2ly} translates a Type@tie{}1 MIDI file to a LilyPond source
+@c ommand{midi2ly} converts tracks into @rinternals{Staff} and
+@c ommand{midi2ly} tries to compensate for these timing errors, but is not
+@c ode{:1}.
+@node Invoking musicxml2ly
+@section Invoking @code{musicxml2ly}
+
+@untranslated
+
+
+@c index MusicXML
+@c ommand{musicxml2ly} extracts the notes, articulations, score structure,
+@node Invoking abc2ly
+@section Invoking @code{abc2ly}
+
+@untranslated
+
+
+@c index ABC
+@quotation
+@end quotation
+@c ommand{abc2ly} translates from ABC to LilyPond. It is invoked as follows:
+@c ommand{abc2ly} does not.
+@c ommand{abc2ly} ignores the ABC beaming.
+@node Invoking etf2ly
+@section Invoking @command{etf2ly}
+
+@untranslated
+
+
+@c index ETF
+@c index enigma
+@c index Finale
+@c index Coda Technology
+@node Generating LilyPond files
+@section Generating LilyPond files
+
+@untranslated
+
+
+@c index External programs, generating LilyPond files
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node GNU Free Documentation License
+@appendix GNU Free Documentation License
+
+@untranslated
+
+
+@c index FDL, GNU Free Documentation License
+@c enter Version 1.1, March 2000
+@subheading ADDENDUM: How to use this License for your documents
+@c Local Variables:
+@c ispell-local-pdict: "ispell-dict"
+@c End:
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@c Note: keep this node named so that `info lilypond-book' brings you here.
+@node lilypond-book
+@chapter Running @command{lilypond-book}
+
+@untranslated
+
+
+@c ommand{lilypond-book} provides a way to automate this process: This
+@c ommand{lilypond} on them, and outputs the document with pictures
+@c ode{lilypond-book}, see FIXME FIXME @c @ref{Setup for MacOS X}.
+@c index texinfo
+@c index latex
+@c index texinfo
+@c index texi
+@c index html
+@c index docbook
+@c index documents, adding music to
+@c index HTML, music in
+@c index Texinfo, music in
+@c index DocBook, music in
+@c index @LaTeX{}, music in
+@menu
+* An example of a musicological document::
+* Integrating music and text::
+* Music fragment options::
+* Invoking lilypond-book::
+* Filename extensions::
+* Alternate methods of mixing text and music::
+@end menu
+
+@node An example of a musicological document
+@section An example of a musicological document
+
+@untranslated
+
+
+@c index musicology
+@subheading Input
+@quotation
+@end quotation
+@subheading Processing
+@c keep space after @version{} so TeX doesn't choke
+@subheading Output
+@c ode{\lilypondfile}.
+@node Integrating music and text
+@section Integrating music and text
+
+@untranslated
+
+
+@menu
+* LaTeX::
+* Texinfo::
+* HTML::
+* DocBook::
+@end menu
+
+@node LaTeX
+@subsection @LaTeX{}
+
+@untranslated
+
+
+@c ode{\lilypond@{@}}, so this command is only useful with the
+@c ode{fragment} option.
+@c ode{\begin@{document@}}. The @command{lilypond-book} command sends
+@c index titling and lilypond-book
+@c index \header in @LaTeX{} documents
+@c ode{lilypond-book} has split the snippet into several PostScript
+@c index Latex, feta symbols
+@c index fetachar
+@ref{Invoking lilypond-book}.
+@node Texinfo
+@subsection Texinfo
+
+@untranslated
+
+
+@node HTML
+@subsection HTML
+
+@untranslated
+
+
+@c ommand{lilypond-book} then produces an HTML file with appropriate image
+@c index titling in HTML
+@c index preview image
+@c index thumbnail
+@node DocBook
+@subsection DocBook
+
+@untranslated
+
+
+@subheading Common conventions
+@c ode{inlinemediaobject} element, so our snippets can be formatted
+@c ommand{lilypond-book} should have the extension @file{.lyxml}.
+@subheading Including a LilyPond file
+@subheading Including LilyPond code
+@c ode{inlinemediaobject}, and there is a @code{textobject} containing
+@subheading Processing the DocBook document
+@node Music fragment options
+@section Music fragment options
+
+@untranslated
+
+
+@c ode{ragged-right = ##t} is added to the LilyPond snippet. This is the
+@c ode{pt}. This option affects LilyPond output (this is, the staff
+@c ode{ragged-right} option.
+@c ode{cm}, @code{mm}, @code{in}, or @code{pt}. This option affects
+@c ode{noindent} is redundant normally.
+@c ode{relative} option only works when @code{fragment} option is set,
+@c ode{intertext} option (not implemented yet); then the actual music is
+@c ode{LYDOC_LOCALEDIR} to a directory path; the directory should
+@c ode{@@documentlanguage @var{LANG}} and @file{foo@/.ly} header
+@c ode{verbatim} option) is put into a quotation block. This option is
+@c ode{texidoc} documentation block.
+@c ode{texidoc} option: if @command{lilypond} is called with the
+@c ode{\header}, it creates a file @file{foo@/.doctitle}. When
+@c ode{doctitle} option is used, the contents of @file{foo@/.doctitle},
+@c ode{@@lydoctitle} should be a macro defined in the Texinfo document.
+@node Invoking lilypond-book
+@section Invoking @command{lilypond-book}
+
+@untranslated
+
+
+@c ommand{lilypond-book} produces a file with one of the following
+@subheading Format-specific instructions
+@subsubheading @LaTeX{}
+@c ommand{dvips}. The first way is simpler and recommended@footnote{Note
+@c index outline fonts
+@c index type1 fonts
+@c index dvips
+@c index invoking dvips
+@c ommand{dvips} options.
+@subsubheading Texinfo
+@c ommand{texi2dvi} or @command{makeinfo}, depending on the output format
+@subheading Command line options
+@c ommand{lilypond-book} accepts the following command line options:
+@c ode{texi} (the default) or @code{docbook}. If this option is missing,
+@c ommand{lilypond-book} tries to detect the format automatically, see
+@ref{Filename extensions}. Currently, @code{texi} is the same as
+@c ode{texi-html}.
+@c This complicated detail is not implemented, comment it out -jm
+@c ommand{latex} with the same @code{-I @var{dir}} options.
+@c ommand{lilypond-book} generates lots of small files that LilyPond will
+@c ode{lilypond}. @code{lilypond-book} will not @code{--filter} and
+@c ode{--process} at the same time.
+@node Filename extensions
+@section Filename extensions
+
+@untranslated
+
+
+@quotation
+@end quotation
+@c ommand{lilypond-book} running, otherwise it will exit with an error
+@node Alternate methods of mixing text and music
+@section Alternative methods of mixing text and music
+
+@untranslated
+
+
+@menu
+* Many quotes from a large score::
+* Inserting LilyPond output into OpenOffice.org::
+* Inserting LilyPond output into other programs::
+@end menu
+
+@node Many quotes from a large score
+@unnumberedsubsec Many quotes from a large score
+
+@untranslated
+
+
+@node Inserting LilyPond output into OpenOffice.org
+@unnumberedsubsec Inserting LilyPond output into OpenOffice.org
+
+@untranslated
+
+
+@c index OpenOffice.org
+@node Inserting LilyPond output into other programs
+@unnumberedsubsec Inserting LilyPond output into other programs
+
+@untranslated
+
+
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: us-ascii; mode: texinfo; -*-
+@include version.itexi
+@include common-macros.itexi
+@c ***** Displaying text *****
+@c To get decent quotes in `foo' and ``foo''.
+@c artouche
+@quotation
+@quotation
+@c artouche
+@end quotation
+@end quotation
+@c ***** Headings in a doc subsection *****
+@c Don't insert an empty line after @predefined! Right now
+@c it doesn't matter, but a future implementation will probably
+@c add some code which needs this restriction.
+@subsubheading Predefined commands
+@c The next macro is a dummy currently since texinfo doesn't
+@c provide a real ragged-right environment yet.
+@c
+@c Due to a bug in texi2html (texi2html.pl CVS versions <= 1.245)
+@c the macro must not be empty.
+@c
+@subsubheading Selected Snippets
+@c Don't insert an empty line after @seealso! Otherwise we get
+@c unwanted extra vertical space in the PDF output.
+@subsubheading See also
+@subsubheading Known issues and warnings
+@c ***** Links and references *****
+@c Definitions for references:
+@c
+@c @rglos
+@c @rlearning
+@c @ruser
+@c @ressay
+@c @rprogram
+@c @rlsr
+@c @rinternals
+@c
+@c All these also have a @...named version which allows to specify the
+@c displayed text for the reference as second argument.
+@c
+@c ***** HTML + bigpage is a special case (other manual names); all other
+@c formats are treated similarly.
+@c *** not TeX ***
+@ifnottex
+@c ** bigpage **
+@ref{\TEXT\,,,music-glossary-big-page,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary-big-page,Music Glossary}
+@ref{\TEXT\,,,learning-big-page,Learning Manual}
+@ref{\TEXT\,,\DISPLAY\,learning-big-page,Learning Manual}
+@ref{\TEXT\,,,notation-big-page,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation-big-page,Notation Reference}
+@ref{\TEXT\,,,essay-big-page,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay-big-page,Essay}
+@ref{\TEXT\,,,application-big-page,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application-big-page,Application Usage}
+@ref{\TEXT\,,,snippets-big-page,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets-big-page,Snippets}
+@ref{\TEXT\,,,internals-big-page,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals-big-page,Internals Reference}
+@c ** not bigpage **
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,,notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation,Notation Reference}
+@ref{\TEXT\,,,essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@ref{\TEXT\,,,application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application,Application Usage}
+@ref{\TEXT\,,,snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets,Snippets}
+@ref{\TEXT\,,,internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals,Internals Reference}
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@ref{\TEXT\,,,lilypond-notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,lilypond-notation,Notation Reference}
+@ref{\TEXT\,,,lilypond-essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,lilypond-essay,Essay}
+@ref{\TEXT\,,,lilypond-application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,lilypond-application,Application Usage}
+@ref{\TEXT\,,,lilypond-snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,lilypond-snippets,Snippets}
+@ref{\TEXT\,,,lilypond-internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,lilypond-internals,Internals Reference}
+@end ifnottex
+@c *** TeX ***
+@c All commands below should work in the middle of the line;
+@c we thus must not use @vindex directly since it works only if placed
+@c on a line of its own. To overcome this problem, we define a
+@c replacement macro using the internal definition of @vindex which
+@c delimits arguments in the standard way (i.e., with braces).
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,\DISPLAY\,learning,Learning Manual}
+@ref{\TEXT\,,,notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation,Notation Reference}
+@ref{\TEXT\,,,essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@ref{\TEXT\,,,application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application,Application Usage}
+@ref{\TEXT\,,,snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets,Snippets}
+@ref{\TEXT\,,,internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals,Internals Reference}
+@c ***** Macros specific to the web site *****
+@c LEGALESE
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Running lilypond
+@chapter Running @command{lilypond}
+
+@untranslated
+
+
+@menu
+* Normal usage::
+* Command-line usage::
+* Error messages::
+@end menu
+
+@node Normal usage
+@section Normal usage
+
+@untranslated
+
+
+@c @rlearning{First steps} if
+@node Command-line usage
+@section Command-line usage
+
+@untranslated
+
+
+@c @ref{Setup for MacOS X}.
+@menu
+* Invoking lilypond::
+* Command line options for lilypond::
+* Environment variables::
+@end menu
+
+@node Invoking lilypond
+@subsection Invoking @command{lilypond}
+
+@untranslated
+
+
+@c ode{output-suffix} will be inserted between the basename and the
+@node Command line options for lilypond
+@subsection Command line options for @command{lilypond}
+
+@untranslated
+
+
+@c index Invoking @command{lilypond}
+@c index command line options for @command{lilypond}
+@c index options, command line
+@c index switches
+@c ode{svg}, @code{ps}, @code{pdf}, and @code{png}.
+@c index point and click, command line
+@c index help, command line
+@c index paper-size, command line
+@c Match " in previous line to help context-sensitive editors
+@c index safe, command line
+@c ode{--safe} or the @code{--jail} option @b{MUST} be passed. The
+@c ode{--safe} option will prevent inline Scheme code from wreaking
+@quotation
+@end quotation
+@c ode{-dsafe} does @emph{not} detect resource overuse. It is still possible to
+@c index output format, setting
+@c index PostScript output
+@c index Postscript, encapulated
+@c index EPS (Encapsulated PostScript)
+@c index SVG (Scalable Vector Graphics)
+@c index Scheme dump
+@c index preview, command line
+@c index file searching
+@c index search path
+@c index PostScript output
+@c index Portable Network Graphics (PNG) output
+@c ode{--ps}. The resolution in DPI of the image may be set with
+@c index Portable Document Format (PDF) output
+@c ode{--safe} when LilyPond formatting is available through a web
+@c ode{--jail} to work @command{lilypond} must be run as root, which is usually
+@c ode{nosuid}. In this way, it is impossible to run executables or to
+@node Environment variables
+@subsection Environment variables
+
+@untranslated
+
+
+@c index LANG
+@c index LILYPOND_DATADIR
+@c ommand{lilypond} recognizes the following environment variables:
+@node Error messages
+@section Error messages
+
+@untranslated
+
+
+@c index error messages
+@c index warning
+@c index error
+@c index fatal error
+@c index trace, Scheme
+@c index call trace
+@c index Scheme error
+@c ode{--verbose}) then a call trace of the offending
+@c index Programming error
+@c index errors, message format
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Suggestions for writing files
+@chapter Suggestions for writing files
+
+@untranslated
+
+
+@menu
+* General suggestions::
+* Typesetting existing music::
+* Large projects::
+@end menu
+
+@node General suggestions
+@section General suggestions
+
+@untranslated
+
+
+@node Typesetting existing music
+@section Typesetting existing music
+
+@untranslated
+
+
+@c ode{showLastLength} or @code{showFirstLength} properties to speed up
+@node Large projects
+@section Large projects
+
+@untranslated
+
+
+@c ode{\score} section is the most likely thing to change;
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Updating files with convert-ly
+@chapter Updating files with @command{convert-ly}
+
+@untranslated
+
+
+@c index Updating a LilyPond file
+@c index convert-ly
+@menu
+* Invoking convert-ly::
+* Command line options for convert-ly::
+* Problems with convert-ly::
+@end menu
+
+@node Invoking convert-ly
+@section Invoking @command{convert-ly}
+
+@untranslated
+
+
+@c ommand{convert-ly} uses @code{\version} statements in the input
+@c ode{myfile.ly} in-place and preserve the original file in
+@c ode{myfile.ly~}.
+@c ommand{convert-ly} always converts up to the last syntax change
+@c ode{Compile > Update syntax}.
+@c ode{Start > Accessories > Command Prompt}.
+@node Command line options for convert-ly
+@section Command line options for @command{convert-ly}
+
+@untranslated
+
+
+@node Problems with convert-ly
+@section Problems with @code{convert-ly}
+
+@untranslated
+
+
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of application.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Working on LilyPond projects
+@chapter Working on LilyPond projects
+
+@untranslated
+
+
+@menu
+* When things don't work::
+* Make and Makefiles::
+@end menu
+
+@node When things don't work
+@section When things don't work
+
+@untranslated
+
+
+@menu
+* Updating old input files::
+* Common errors::
+* Troubleshooting (taking it all apart)::
+* Minimal examples::
+@end menu
+
+@node Updating old input files
+@subsection Updating old input files
+
+@untranslated
+
+
+@c index convert-ly
+@c index updating old input files
+@c ode{convert-ly}. For details about how to run this program, see
+@c ode{No\"el} (this would print the French word for
+@c keep "-matching straight in fancy editors
+@c ode{ë} must be entered directly into the LilyPond file as an
+@node Common errors
+@subsection Common errors
+
+@untranslated
+
+
+@menu
+* Music runs off the page::
+* An extra staff appears::
+* Apparent error in ../ly/init.ly::
+* Error message Unbound variable %::
+* Error message FT_Get_Glyph_Name::
+@end menu
+
+@node Music runs off the page
+@unnumberedsubsubsec Music runs off the page
+
+@untranslated
+
+
+@node An extra staff appears
+@unnumberedsubsubsec An extra staff appears
+
+@untranslated
+
+
+@c ode{\relative} blocks, which each implicitly create @code{Staff}
+@c ode{\relative} commands, like this:
+@node Apparent error in ../ly/init.ly
+@unnumberedsubsubsec Apparent error in @code{../ly/init.ly}
+
+@untranslated
+
+
+@c ode{../ly/init.ly} if the input file is not correctly formed,
+@c ode{score} block is correctly terminated. The correct structure
+@c keep "-matching straight in fancy editors
+@node Error message Unbound variable %
+@unnumberedsubsubsec Error message Unbound variable %
+
+@untranslated
+
+
+@node Error message FT_Get_Glyph_Name
+@unnumberedsubsubsec Error message FT_Get_Glyph_Name
+
+@untranslated
+
+
+@node Troubleshooting (taking it all apart)
+@subsection Troubleshooting (taking it all apart)
+
+@untranslated
+
+
+@c ode{\bass} in the @code{\score} uncommented.
+@c ode{bass} part until you find the problem line.
+@node Minimal examples
+@subsection Minimal examples
+
+@untranslated
+
+
+@node Make and Makefiles
+@section Make and Makefiles
+
+@untranslated
+
+
+@c index makefiles
+@c index make
+@c ode{Makefile} that defines what files depend on what others and what
+@c ode{ballad.pdf} and @code{ballad.midi} from @code{ballad.ly} by
+@c ode{lilypond-book} projects). Makefiles vary greatly in
+@c ode{make}, as what follows here gives only a glimpse of what it
+@c ode{Parts} directories get their notes from @code{.ily}
+@c ode{Advanced}. Click @code{Environment Variables}, and then
+@c ode{edit}, and add the path to the GNU Make executable file, which
+@c ommand{latex} command be run twice to update links. Output files are
+@c ode{htmlout} directory for the html output.
+@c @rprogram{Setup for MacOS X},
+
+@c -- SKELETON FILE --
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+
+
+@c Don't replace quotes with directed quotes.
+
+@set txicodequoteundirected
+@set txicodequotebacktick
+
+
+@c ***** Displaying text *****
+
+@c We need this since @q{\} doesn't work with makeinfo 4.11 --
+@c say @q{@bs{}} instead.
+
+@macro bs
+\\
+@end macro
+
+
+@ifnotinfo
+
+@macro notation{TEXT}
+@var{\TEXT\}
+@end macro
+
+@end ifnotinfo
+
+@ifinfo
+
+@macro notation{TEXT}
+\TEXT\
+@end macro
+
+@end ifinfo
+
+
+@macro smallspace
+@sp 1
+@end macro
+
+
+@c ***** Displaying images not generated by lilypond-book *****
+
+@c Current installation setup of Info docs requires that all images are
+@c expected to be found in the `lilypond/' subdirectory. `lilypond-book'
+@c already generates proper @image commands for images of music; these
+@c macro definitions do the same for other images.
+
+@ifnotinfo
+
+@macro sourceimage{FILENAME,WIDTH,HEIGHT,ALTTEXT}
+@image{pictures/\FILENAME\,\WIDTH\,\HEIGHT\,\ALTTEXT\}
+@end macro
+
+@end ifnotinfo
+
+@ifinfo
+
+@macro sourceimage{FILENAME,WIDTH,HEIGHT,ALTTEXT}
+@image{lilypond/pictures/\FILENAME\,\WIDTH\,\HEIGHT\,\ALTTEXT\}
+@end macro
+
+@end ifinfo
+
+
+@c ***** Headers *****
+
+@ifclear snippets-sections
+@macro lydoctitle {TEXT}
+@need 600
+@emph{\TEXT\}
+@end macro
+@end ifclear
+
+@c ***** Indexing *****
+
+@c Don't remove the `@c' within the macro definition! See section 19.3,
+@c `Macro Details and Caveats', in the texinfo info file for explanation.
+
+@macro funindex {TEXT}
+@findex \TEXT\
+@kindex \TEXT\
+@c
+@end macro
+
+
+@c ***** Macros specific to translated docs *****
+
+@c ugh, cannot set/define global variable 'translationof' in any way :-(
+
+@iftex
+
+@macro translationof{TEXT}
+@end macro
+
+@end iftex
+
+@ifinfo
+
+@macro translationof{TEXT}
+@set translationof \TEXT\
+@end macro
+
+@end ifinfo
+
+@ifhtml
+
+@ifset bigpage
+@macro untranslated
+@end macro
+@end ifset
+
+@ifclear bigpage
+@macro untranslated
+UNTRANSLATED NODE: IGNORE ME
+@end macro
+@end ifclear
+
+@end ifhtml
+
+@ifnothtml
+
+@macro untranslated
+@end macro
+
+@end ifnothtml
+
+
+@c ***** Macros specific to the web site *****
+
+@ifset web
+
+@macro help{TEXT}
+@html
+<div class="help">
+<strong>
+ <span style="text-decoration:blink">Help wanted:</span>
+</strong> \TEXT\
+</div>
+@end html
+@end macro
+
+@macro divId {ID}
+@html
+<div id="\ID\">
+@end html
+@end macro
+
+@macro divClass {CLASS}
+@html
+<div class="\CLASS\">
+@end html
+@end macro
+
+@macro divEnd
+@c keep the space for proper nesting of </p>
+
+@html
+</div>
+@end html
+@end macro
+
+
+@c not strictly necessary, but it makes things easier for updating news
+@macro newsItem
+@html
+<div class="news-item">
+@end html
+@end macro
+
+@macro newsEnd
+@c keep the space for proper nesting of </p>
+
+@html
+</div>
+@end html
+@end macro
+
+
+
+@macro imageClickable{IMAGE-FILE, MORE-TEXT, CLICK-FILE, POSITION}
+@html
+<div class="float-\POSITION\">
+ <a class="clickable" href="\CLICK-FILE\">
+ <img src="\IMAGE-FILE\" alt="\IMAGE-FILE\">
+ </a>
+ <p style="text-align: center">
+ \MORE-TEXT\
+ </p>
+</div>
+@end html
+@ifnothtml
+FIXME: broken image
+@c @image{\IMAGE-FILE\}
+@end ifnothtml
+@end macro
+
+@macro imageFloat{IMAGE-FILE, POSITION}
+@html
+<img class="float-\POSITION\" src="pictures/\IMAGE-FILE\" alt="\IMAGE-FILE\">
+@end html
+@ifnothtml
+FIXME: broken image
+@c @image{\IMAGE-FILE\}
+@end ifnothtml
+@end macro
+
+@macro imageId{ID, IMAGE-FILE, ALT}
+@html
+<div id="\ID\">
+ <img src="pictures/\IMAGE-FILE\" alt="\ALT\">
+</div>
+@end html
+@ifnothtml
+FIXME: broken image
+@c @image{\IMAGE-FILE\}
+@end ifnothtml
+@end macro
+
+@end ifset
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; documentlanguage: fr -*-
+
+@ignore
+ Translation of GIT committish: d56aa8181857c5feabf303ae88e716eba069f0a9
+
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+@c \version "2.12.0"
+
+@quotation
+Nous souhaitons dédier ce programme à tous les amis que nous avons
+rencontrés par la musique.
+
+Han-Wen et Jan
+@end quotation
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of general.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@setfilename general.info
+@settitle LilyPond -- Muzieknotatie voor iedereen
+@documentencoding UTF-8
+@documentlanguage en
+@set web
+@include macros.itexi
+@afourpaper
+@ifnottex
+@node Top
+@top
+
+@translationof Top
+
+
+@chapheading
+@end ifnottex
+@finalout
+@titlepage
+@title LilyPond
+@subtitle
+@titlefont{New Website}
+@author Het LilyPond ontwikkelteam
+@quotation
+@end quotation
+@vskip 20pt
+@end titlepage
+@copying
+@quotation
+@end quotation
+@end copying
+@divId{pageHeader}
+@heading LilyPond
+
+... muzieknotatie voor iedereen
+@divEnd
+@c @imageId{cmws,web-clef-g-eight-alpha.png,Catchy Musical Web Snippet}
+@imageId{lilylogo,double-lily-modified3.png,LilyPond logo}
+@c @im ageId{cmws,web-snippet-alpha.png,Catchy Musical Web Snippet}
+@divId{quickSummary}
+@subheading Wat is LilyPond?
+TODO FIXME DUTCH
+
+LilyPond is an open-source music engraving program, devoted to
+producing the highest-quality sheet music possible. We bring the
+aesthetics of traditionally engraved music to computer printouts.
+
+LilyPond is Free Software and part of the
+@uref{http://@/www@/.gnu@/.org/, GNU} project.
+
+@divClass{align-right}
+@divEnd
+@divEnd
+@divId{news}
+@include news-front.itexi
+@divClass{float-right}
+Lees de @ref{Introduction}!
+
+@divEnd
+@divEnd
+@divId{latestVersion}
+@subheading Quick links
+@c TODO: javascript to detect OS and suggest download?
+@subsubheading Stable
+@ref{Download, Download 2.12.3}
+@ref{Manuals, Manuals 2.12.3}
+@subsubheading Unstable
+@ref{Development, Download 2.13.2}
+@ref{Development, Manuals 2.13.2}
+@divEnd
+@divClass{hide}
+@menu
+* Introduction::
+* Download::
+* Manuals::
+* Community::
+@end menu
+
+@divEnd
+@contents
+@include general/introduction.itexi
+@include general/download.itexi
+@include general/manuals.itexi
+@include general/community.itexi
+@bye
+
--- /dev/null
+depth = ../../..
+
+LOCALSTEPMAKE_TEMPLATES = ly
+
+include $(depth)/make/stepmake.make
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of general.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c Don't replace quotes with directed quotes.
+@set txicodequoteundirected
+@set txicodequotebacktick
+@c ***** Displaying text *****
+@c We need this since @q{\} doesn't work with makeinfo 4.11 --
+@c say @q{@bs{}} instead.
+@c ***** Displaying images not generated by lilypond-book *****
+@c Current installation setup of Info docs requires that all images are
+@c expected to be found in the `lilypond/' subdirectory. `lilypond-book'
+@c already generates proper @image commands for images of music; these
+@c macro definitions do the same for other images.
+@c ***** Headers *****
+@c ***** Indexing *****
+@c Don't remove the `@c' within the macro definition! See section 19.3,
+@c `Macro Details and Caveats', in the texinfo info file for explanation.
+@c
+@c ***** Macros specific to translated docs *****
+@c ugh, cannot set/define global variable 'translationof' in any way :-(
+@set translationof \TEXT\
+@c ***** Macros specific to the web site *****
+@c keep the space for proper nesting of </p>
+@c not strictly necessary, but it makes things easier for updating news
+@c keep the space for proper nesting of </p>
+@c @image{\IMAGE-FILE\}
+@c @image{\IMAGE-FILE\}
+@c @image{\IMAGE-FILE\}
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of general.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node Community
+@unnumbered Community
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Interacting with the community
+@ref{Contact}: get help, discuss, and keep in touch!
+@ref{Tiny examples}: these are @emph{highly} recommended when
+@ref{Bug reports}: something went wrong.
+@divEnd
+@divClass{column-left-bottom}
+@subheading Making LilyPond better
+@ref{Help us}: your assistance is requested.
+@ref{Development}: for contributors and testers.
+@ref{Authors}: the people who made LilyPond what it is today.
+@divEnd
+@divClass{column-right-bottom}
+@subheading Miscellaneous
+@ref{Publications}: what we wrote, and have had written about us.
+@ref{Old news}: an archive.
+@divEnd
+@divClass{hide}
+@menu
+* Contact::
+* Tiny examples::
+* Bug reports::
+* Help us::
+* Development::
+* Authors::
+* Publications::
+* Old news::
+@end menu
+
+@divEnd
+@node Contact
+@unnumberedsec Contact
+
+@untranslated
+
+
+@divClass{column-left-bottom}
+@subheading User Discussions and Help
+@subsubheading User mailist: @code{lilypond-user@@gnu.org}
+@quotation
+@end quotation
+@subsubheading IRC
+@subsubheading Other languages
+@divEnd
+@divClass{column-right-top}
+@subheading Stay Informed
+@subsubheading LilyPond Report
+@subsubheading Releases mailist: @code{info-lilypond@@gnu.org}
+@quotation
+@c don't include gmane posting here. -gp
+@end quotation
+@divEnd
+@divClass{column-right-bottom}
+@subheading Developer Discussion
+@subsubheading Developer mailist: @code{lilypond-devel@@gnu.org}
+@quotation
+@end quotation
+@subsubheading Bug mailist: @code{bug-lilypond@@gnu.org}
+@quotation
+@c don't include gmane posting here. -gp
+@end quotation
+@divEnd
+@node Tiny examples
+@unnumberedsec Tiny examples
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading What are @qq{Tiny examples}?
+@divEnd
+@divClass{column-left-bottom}
+@subheading Why create them?
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-right-bottom}
+@subheading How do I create them?
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@node Bug reports
+@unnumberedsec Bug reports
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Step 1: Known bugs
+@divEnd
+@divClass{column-left-bottom}
+@subheading Step 2: Creating a bug report
+@divEnd
+@divClass{column-right-bottom}
+@subheading Step 3: Sending a bug report
+@divEnd
+@node Help us
+@unnumberedsec Help us
+
+@untranslated
+
+
+@subheading This document
+@subsubheading High priority / blocks release
+@subsubheading Low priority / may never
+@node Development
+@unnumberedsec Development
+
+@untranslated
+
+
+@divClass{heading-center}
+@heading Development materials for LilyPond 2.13.3
+@ref{Manuals}.}
+@divEnd
+@divClass{column-left-bottom}
+@subheading Download
+@subheading Manuals
+@divEnd
+@divClass{column-right-bottom}
+@subheading Contributors' Guide
+@divEnd
+@node Authors
+@unnumberedsec Authors
+
+@untranslated
+
+
+@node Publications
+@unnumberedsec Publications
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading What we wrote
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading What others wrote
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@node Old news
+@unnumberedsec Old news
+
+@untranslated
+
+
+@include general/news.itexi
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of general.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node Download
+@unnumbered Download
+
+@untranslated
+
+
+@divClass{heading-center}
+@heading Downloads for LilyPond 2.12.2
+@divEnd
+@divClass{column-left-top}
+@subheading For users
+@c TODO: duplicate to avoid underlined refs in HTML? icky.
+@ref{Unix, @sourceimage{logo-linux} @sourceimage{logo-freebsd}}
+@ref{Unix, Unix (Linux and FreeBSD)}
+@ref{MacOS X, @sourceimage{logo-macosx}}
+@ref{MacOS X, MacOS X}
+@ref{Windows, @sourceimage{logo-windows}}
+@ref{Windows, Microsoft Windows}
+@divEnd
+@divClass{column-right-top}
+@subheading For developers
+@ref{Source}:
+@ref{Old downloads}:
+@divEnd
+@divClass{column-center-bottom}
+@subheading Software License
+@divEnd
+@divClass{color1}
+@subheading Sponsors
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@divClass{hide}
+@menu
+* Unix::
+* MacOS X::
+* Windows::
+* Source::
+* Old downloads::
+* GPL::
+@end menu
+
+@divEnd
+@node Unix
+@unnumberedsec Unix
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Generic Packages or Distribution-Specific Packages?
+@divEnd
+@divClass{column-left-top}
+@subheading Generic Packages
+@subsubheading Download
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Distribution-specific Packages
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node MacOS X
+@unnumberedsec MacOS X
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Packages
+@subsubheading Download
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Running on the command-line
+@subsubheading Using Python scripts on MacOS 10.3 or 10.4
+@c ommand{convert-ly} and @command{lilypond-book} as follows: if the
+@subsubheading MacOS X on the command line
+@c ommand{abc2ly}, and even @command{lilypond} itself --- are included
+@c ommand{lilypond-book}, @command{convert-ly}, @command{abc2ly}, etc.
+@c ode{bin/convert-ly} (or other program name) in the above file.
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node Windows
+@unnumberedsec Windows
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Packages
+@subsubheading Download
+@subsubheading Install
+@subsubheading Uninstall
+@divEnd
+@divClass{column-right-top}
+@subheading Running on the command-line
+@divEnd
+@divClass{column-center-bottom}
+@subheading Legalese
+@divClass{legal}
+@divEnd
+@divEnd
+@node Source
+@unnumberedsec Source
+
+@untranslated
+
+
+@divClass{column-left-bottom}
+@subheading Source tarball
+@divEnd
+@divClass{column-right-bottom}
+@subheading Compiling instructions
+@divEnd
+@node Old downloads
+@unnumberedsec Old downloads
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading All versions
+@divEnd
+@node GPL
+@unnumberedsec GPL
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Software license
+@divEnd
+@divClass{column-center-bottom}
+@subheading GNU General Public License version 2
+@include gpl-2.0.itexi
+@divEnd
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of general.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node Introduction
+@unnumbered Introduction
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Our Goal
+@imageFloat{flat-design.png,right}
+@divEnd
+@divClass{column-left-top}
+@subheading Why use LilyPond?
+@ref{Features}: What can LilyPond do?
+@ref{Examples}: I want to see some music!
+@ref{Freedom}: LilyPond is Free Software.
+@divEnd
+@divClass{column-right-top}
+@subheading Who uses it?
+@ref{Productions}: Real-life use of LilyPond.
+@ref{Testimonials}: What do people say?
+@divEnd
+@divClass{column-center-bottom}
+@subheading Why not use LilyPond?
+@ref{Text input}: You write music as @emph{text}?!
+@divEnd
+@divClass{hide}
+@menu
+* Features::
+* Examples::
+* Freedom::
+* Productions::
+* Testimonials::
+* Text input::
+@end menu
+
+@divEnd
+@node Features
+@unnumberedsec Features
+
+@untranslated
+
+
+@subheading Why switch to LilyPond?
+@subsubheading Excellent classical engraving
+@imageFloat{flat-design.png,right}
+@subsubheading No fiddling
+@subsubheading Text-based input
+@subsubheading Mix music and text
+@imageFloat{lilypond-book.png,right}
+@subsubheading Free software
+@subsubheading Extensible design
+@subsubheading Excellent support
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Text input}.
+@divEnd
+@node Examples
+@unnumberedsec Examples
+
+@untranslated
+
+
+@subsubheading Classical Music
+@subsubheading Complex Notation
+@subsubheading Early Music
+@subsubheading Modern Music
+@subsubheading Efficient, flexible creation of performance materials
+@subsubheading Tablature
+@subsubheading Schenker Graphs
+@subsubheading Vocal Music
+@subsubheading Educational Applications
+@subsubheading Popular Music
+@subsubheading Large Projects
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Freedom}. If you've already decided to try LilyPond, first
+@divEnd
+@node Freedom
+@unnumberedsec Freedom
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Free Software
+@ref{GPL, GNU General Public License} and the @ref{FDL, GNU Free
+@divEnd
+@c @divClass{column-left-top}
+@divClass{color2}
+@divClass{keep-bullets}
+@subheading What are the benefits to users?
+@divEnd
+@divEnd
+@c @divClass{column-right-top}
+@divClass{color3}
+@divClass{keep-bullets}
+@subheading Why do LilyPond developers @qq{give away} their work for free?
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Productions} and sheet music. If you've already decided to
+@divEnd
+@node Productions
+@unnumberedsec Productions
+
+@untranslated
+
+
+@divClass{column-left-top}
+@subheading Concerts
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-right-top}
+@subheading Published sheet music
+@divClass{keep-bullets}
+@divEnd
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Text input}.
+@divEnd
+@node Testimonials
+@unnumberedsec Testimonials
+
+@untranslated
+
+
+@divClass{testimonial-item}
+@imageFloat{carter-brey.jpg, right}
+@subsubheading @uref{http://nyphil.org/meet/orchestra/index.cfm?page=profile&personNum=7, Carter Brey}, Principal Cellist, New York Philharmonic
+@divEnd
+@divClass{testimonial-item}
+@imageFloat{orm-finnendahl.jpg, left}
+@subsubheading @uref{http://icem-www.folkwang-hochschule.de/~finnendahl/, Orm Finnendahl}, professor of Composition, Musikhochschule Freiburg
+@divEnd
+@divClass{testimonial-item}
+@imageFloat{darius-blasband.jpg, right}
+@subsubheading Darius Blasband, composer (Brussels, Belgium)
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Kieren MacMillan, composer (Toronto, Canada)
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Chris Cannam, lead programmer of the @uref{http://www.rosegardenmusic.com/, RoseGarden} project.
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Chris Snyder, @uref{http://www.adoromusicpub.com/, Adoro Music Publishing}
+@divEnd
+@divClass{testimonial-item}
+@subsubheading David Bobroff, Bass Trombone, Iceland Symphony Orchestra
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Vaylor Trucks, Electric guitar player (Yes, @uref{http://www.allmanbrothersband.com/modules.php?op=modload&name=userpage&file=content&page_id=12, related to})
+@divEnd
+@divClass{testimonial-item}
+@subsubheading @uref{http://nicolas.sceaux.free.fr/, Nicolas Sceaux}, @uref{http://www.mutopiaproject.org/, Mutopia} contributor
+@divEnd
+@divClass{testimonial-item}
+@subsubheading @uref{http://www.troff.org/whoswho.html#werner, Werner Lemberg}, Conductor at the Theatre in Koblenz, Germany and distinguished GNU Hacker.
+@divEnd
+@divClass{testimonial-item}
+@subsubheading Paul Davis, developer of @uref{http://jackaudio.org/, JACK} and @uref{http://www.ardour.org/, Ardour}.
+@divEnd
+@divClass{column-center-bottom}
+@subheading Where now?
+@divEnd
+@node Text input
+@unnumberedsec Text input
+
+@untranslated
+
+
+@c TRANSLATORS: so far it's mostly from
+@c http://lilypond.org/web/switch/howto
+@subheading @qq{Compiling} Music
+@subsubheading It's as simple as A B C
+@imageFloat{text-input-1-annotate.png,center}
+@imageFloat{text-input-1-output.png,center}
+@imageFloat{text-input-2-annotate.png,center}
+@imageFloat{text-input-2-output.png,center}
+@subsubheading Pop music
+@imageFloat{text-input-pop-annotate.png,center}
+@imageFloat{text-input-pop-output.png,center}
+@subsubheading Orchestral parts
+@imageFloat{text-input-parts-both-annotate.png,center}
+@imageFloat{text-input-parts-single-annotate.png,center}
+@imageFloat{text-input-parts-single-output.png,center}
+@imageFloat{text-input-score-annotate.png,center}
+@imageFloat{text-input-score-output.png,center}
+@subsubheading Beginner Documentation
+@subsubheading Easier editing environments
+@divClass{column-center-bottom}
+@subheading Where now?
+@ref{Freedom} that LilyPond provides, or read about users'
+@ref{Productions} and @ref{Testimonials}.
+@divEnd
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of general.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: us-ascii; mode: texinfo; -*-
+@include version.itexi
+@include common-macros.itexi
+@c ***** Displaying text *****
+@c To get decent quotes in `foo' and ``foo''.
+@c artouche
+@quotation
+@quotation
+@c artouche
+@end quotation
+@end quotation
+@c ***** Headings in a doc subsection *****
+@c Don't insert an empty line after @predefined! Right now
+@c it doesn't matter, but a future implementation will probably
+@c add some code which needs this restriction.
+@subsubheading Predefined commands
+@c The next macro is a dummy currently since texinfo doesn't
+@c provide a real ragged-right environment yet.
+@c
+@c Due to a bug in texi2html (texi2html.pl CVS versions <= 1.245)
+@c the macro must not be empty.
+@c
+@subsubheading Selected Snippets
+@c Don't insert an empty line after @seealso! Otherwise we get
+@c unwanted extra vertical space in the PDF output.
+@subsubheading See also
+@subsubheading Known issues and warnings
+@c ***** Links and references *****
+@c Definitions for references:
+@c
+@c @rglos
+@c @rlearning
+@c @ruser
+@c @ressay
+@c @rprogram
+@c @rlsr
+@c @rinternals
+@c
+@c All these also have a @...named version which allows to specify the
+@c displayed text for the reference as second argument.
+@c
+@c ***** HTML + bigpage is a special case (other manual names); all other
+@c formats are treated similarly.
+@c *** not TeX ***
+@ifnottex
+@c ** bigpage **
+@ref{\TEXT\,,,music-glossary-big-page,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary-big-page,Music Glossary}
+@ref{\TEXT\,,,learning-big-page,Learning Manual}
+@ref{\TEXT\,,\DISPLAY\,learning-big-page,Learning Manual}
+@ref{\TEXT\,,,notation-big-page,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation-big-page,Notation Reference}
+@ref{\TEXT\,,,essay-big-page,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay-big-page,Essay}
+@ref{\TEXT\,,,application-big-page,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application-big-page,Application Usage}
+@ref{\TEXT\,,,snippets-big-page,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets-big-page,Snippets}
+@ref{\TEXT\,,,internals-big-page,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals-big-page,Internals Reference}
+@c ** not bigpage **
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,,notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation,Notation Reference}
+@ref{\TEXT\,,,essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@ref{\TEXT\,,,application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application,Application Usage}
+@ref{\TEXT\,,,snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets,Snippets}
+@ref{\TEXT\,,,internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals,Internals Reference}
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@ref{\TEXT\,,,lilypond-notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,lilypond-notation,Notation Reference}
+@ref{\TEXT\,,,lilypond-essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,lilypond-essay,Essay}
+@ref{\TEXT\,,,lilypond-application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,lilypond-application,Application Usage}
+@ref{\TEXT\,,,lilypond-snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,lilypond-snippets,Snippets}
+@ref{\TEXT\,,,lilypond-internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,lilypond-internals,Internals Reference}
+@end ifnottex
+@c *** TeX ***
+@c All commands below should work in the middle of the line;
+@c we thus must not use @vindex directly since it works only if placed
+@c on a line of its own. To overcome this problem, we define a
+@c replacement macro using the internal definition of @vindex which
+@c delimits arguments in the standard way (i.e., with braces).
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,\DISPLAY\,learning,Learning Manual}
+@ref{\TEXT\,,,notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation,Notation Reference}
+@ref{\TEXT\,,,essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@ref{\TEXT\,,,application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application,Application Usage}
+@ref{\TEXT\,,,snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets,Snippets}
+@ref{\TEXT\,,,internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals,Internals Reference}
+@c ***** Macros specific to the web site *****
+@c LEGALESE
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of general.texi
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node Manuals
+@unnumbered Manuals
+
+@untranslated
+
+
+@divClass{heading-center}
+@heading Documentation for LilyPond 2.12.2
+@divEnd
+@divClass{column-center-top}
+@subheading Introduction
+@divEnd
+@divClass{column-left-top}
+@subheading Regular use
+@divEnd
+@divClass{column-right-top}
+@subheading Infrequent Use
+@divEnd
+@divClass{column-center-bottom}
+@subheading Other material
+@divEnd
+@divClass{hide}
+@menu
+* Learning::
+* Glossary::
+* Essay::
+* Notation::
+* Usage::
+* Snippets::
+* FAQ::
+* Changes::
+* Internals::
+* Translated::
+* Old::
+* FDL::
+@end menu
+
+@divEnd
+@c TRANSLATORS: most of the text in this file came from
+@c LM 1.1 About the documentation (before this section was
+@c removed in July 2009).
+@node Learning
+@unnumberedsec Learning
+
+@untranslated
+
+
+@node Glossary
+@unnumberedsec Glossary
+
+@untranslated
+
+
+@node Essay
+@unnumberedsec Essay
+
+@untranslated
+
+
+@node Notation
+@unnumberedsec Notation
+
+@untranslated
+
+
+@node Usage
+@unnumberedsec Usage
+
+@untranslated
+
+
+@node Snippets
+@unnumberedsec Snippets
+
+@untranslated
+
+
+@node FAQ
+@unnumberedsec FAQ
+
+@untranslated
+
+
+@subheading Where are the graphical canvas, menus, and toolbars?
+@subheading There's a lot of documentation! Do I need to read it?
+@subheading That's still a lot of reading! Is it worth it?
+@subheading Something isn't working! How do I fix it?
+@subheading Why do you change the syntax?
+@node Changes
+@unnumberedsec Changes
+
+@untranslated
+
+
+@node Internals
+@unnumberedsec Internals
+
+@untranslated
+
+
+@node Translated
+@unnumberedsec Translated
+
+@untranslated
+
+
+@node Old
+@unnumberedsec Old
+
+@untranslated
+
+
+@node FDL
+@unnumberedsec FDL
+
+@untranslated
+
+
+@divClass{column-center-top}
+@subheading Documentation license
+@divEnd
+@divClass{column-center-bottom}
+@subheading GNU Free Documentation License 1.1
+@include fdl.itexi
+@divEnd
+
+@c -- SKELETON FILE --
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c This file is part of lilypond-general.texi and community.itexi
+
+@c when you add a new item, consider moving the lowest item(s)
+@c into news-old.itexi.
+
+@newsItem
+@subsubheading New Website! @emph{20 Aug 2009}
+
+As you can see, we have a new website design. Many thanks to
+texi2html and CSS for being so flexible!
+
+(FIXME: change date when this is actually announced on lilypond.org)
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.3. @emph{July 2, 2009}
+
+This unstable release contains working menus in OSX 10.5; many
+thanks to Christian Hitz for fixing this long-standing problem!
+This release also contains numerous other bugfixes and features
+such as ties with variable thickness, partially dashed slurs, and
+eyeglasses.
+
+We are planning another 2.12 release in the next week or two,
+which will include the menu fixes for OSX 10.5. Normal users may
+wish to wait for this release rather than using an unstable
+release. For changes and download links, see @ref{Development}.
+@newsEnd
+
+
+
+@newsItem
+@subsubheading Hungarian translation! @emph{22 May 2009}
+
+Elkészült a lilypond.org nagy részének magyar fordítása a LilyPond
+honosítási projekt első lépéseként. A projekt célja a LilyPond
+szabad kottaszedő szoftver minél széleskörűbben elérhetővé tétele
+a magyar felhasználók számára a teljes weboldal és dokumentáció
+lefordítása révén. A teljes dokumentáció lefordításához
+közreműködőket keresünk. Ha részt vennél a honosításban, küldj egy
+e-mailt a harmathdenes AT gmail.com címre!
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond Report #15. @emph{18 May 2009}
+
+The @emph{LilyPond Report} is a short, informal opinion column
+about the LilyPond project: its team, its world, its community.
+Read it @uref{http://news.lilynet.net/The-LilyPond-Report-15,
+here}!
+@newsEnd
+
+
--- /dev/null
+<html>
+<!--
+ Translation of GIT committish: 9dca038856a22595cabab9d8a7565300be2cc363
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+!-->
+ <head>
+ <title>Documentation de LilyPond @TOPLEVEL_VERSION@</title>
+ <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
+ <meta name="aesop" content="links">
+ <meta name="description"
+ content="Top-level index to the standard documentation for
+ LilyPond @TOPLEVEL_VERSION@">
+ </head>
+
+ <body>
+
+ <div class="header">
+ <h1>Documentation de LilyPond</h1>
+ </div>
+
+ <div class="subheader">
+ <p>
+ <strong>Version @TOPLEVEL_VERSION@</strong>
+ <br>
+ <strong>@DATE@</strong>
+ </p>
+ </div>
+
+ <table id="navigation">
+ <tbody>
+ <tr>
+ <td class="left-column">
+ <ul>
+ <li>
+ <a class="title"
+ href="learning/index.fr.html">Manuel d'initiation</a>
+ (partiellement traduit,<br>aussi en <a class="title" href="learning-big-page.fr.html">page
+ unique</a> ~ 1,5 Mo, ou
+ <a class="title" href="learning.fr.pdf">au format PDF</a>)
+ <br>— commencer ici</li>
+ <li><a class="title" href="music-glossary/index.html">Glossaire</a>
+ multilingue<br>(aussi en
+ <a class="title" href="music-glossary-big-page.html">page unique</a>
+ ~ 500 ko, ou <a class="title" href="music-glossary.pdf">au format PDF</a>)
+ <br>— vocabulaire théorique de la musique</li>
+ </ul>
+ </td>
+ <td class="right-column">
+ <ul>
+ <li><a class="title" href="changes.html">Nouveautés</a>
+ <br>— changements depuis la version majeure précédente</li>
+ <li><a class="title" href="../examples.html">Exemples</a>
+ <br>— quelques exemples</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td valign="baseline" class="left-column">
+ <ul>
+ <li>
+ <a class="title" href="notation/index.fr.html">Manuel de notation</a>
+ (partiellement traduit,<br>aussi en <a class="title"
+ href="notation-big-page.fr.html">page unique</a> ~ 4 Mo, ou
+ <a class="title" href="notation.fr.pdf">au format PDF</a>)
+ <br>— gravure de musique avec LilyPond</li>
+ <li>
+ <a class="title" href="internals/index.html">Référence des propriétés internes</a>
+ <br>(en anglais, aussi en <a class="title" href="internals-big-page.html">page
+ unique</a> ~ 1 Mo, <a class="title"
+ href="internals.pdf">au format PDF</a>)
+ <br>— définitions pour les retouches</li>
+ </ul>
+ </td>
+ <td valign="baseline" class="right-column">
+ <ul>
+ <li>
+ <a class="title" href="application/index.fr.html">Utilisation des programmes</a>
+(partiellement traduit,<br>aussi en <a class="title"
+ href="application-big-page.fr.html">page unique</a>, ou
+ <a class="title" href="application.fr.pdf">au format PDF</a>)
+ <br>— installation et exécution des programmes</li>
+ <li><a class="title" href="snippets/index.html">Exemples de code</a>
+(en anglais, aussi en <a class="title" href="snippets-big-page.html">page unique</a> ~ 2 Mo,
+au format <a class="title" href="snippets.pdf">PDF</a>)
+ <br>— petits trucs, astuces et exemples</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td valign="baseline" class="left-column">
+ <ul>
+ <li><a class="title" href="devel.html">Ressources de développement</a>
+ <br>— documentation pour les développeurs et contributeurs</li>
+ </ul>
+ </td><td class="right-column">
+ <ul>
+ <li><a class="title" href="translations.fr.html">État des traductions</a>
+ <br>— avancement des traductions en français</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td valign="baseline" class="left-column">
+ <ul>
+ <li> <a class="title" href="http://lilypond.org/">lilypond.org</a>
+ <br>— le site Web</li>
+ <li>
+ <a class="title" href="http://www.gnu.org/copyleft/gpl.html">Licence</a>
+ <br>— la licence GNU GPL</li>
+ </ul>
+ </td>
+ <td valign="baseline" class="right-column">
+ <ul>
+ <li><a class="title" href="THANKS.html">Remerciements</a>
+ <br>— à nos contributeurs</li>
+ <li><a class="title" href="DEDICATION.html">Dédicace</a>
+ <br>— par Jan et Han-Wen</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td valign="baseline" class="left-column">
+ <ul>
+ </ul>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>
+ Toute la documentation répertoriée sur cette page peut être
+ <strong>téléchargée</strong> :
+ <a href="http://download.linuxaudio.org/lilypond/binaries/documentation/lilypond-@TOPLEVEL_VERSION@-1.documentation.tar.bz2">téléchargement
+ de l'archive compressée</a>.
+ </p>
+ <p>
+ Vous pouvez trouver, au bas de chaque page de cette
+ documentation, des liens vers les <strong>traductions</strong> disponibles.
+ </p>
+ </body>
+</html>
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@setfilename lilypond-learning.info
+@settitle GNU LilyPond Learning Manual
+@documentencoding UTF-8
+@documentlanguage en
+@include macros.itexi
+@c This produces the unified index
+@afourpaper
+@c don't remove this comment.
+@copying
+@quotation
+@end quotation
+@end copying
+@c artouche
+@c @ref{About the documentation}.
+@c TITLE PAGE
+@ifnottex
+@node Top
+@top GNU LilyPond --- Learning Manual
+
+@untranslated
+
+
+@end ifnottex
+@finalout
+@titlepage
+@title LilyPond
+@subtitle The music typesetter
+@titlefont{Learning Manual}
+@author The LilyPond development team
+@vskip 100pt
+@vskip 0pt plus 1filll
+@c @vskip 20pt
+@end titlepage
+@c TOC -- non-tex
+@ifnottex
+@menu
+* Introduction::
+* Common notation::
+* Fundamental concepts::
+* Tweaking output::
+* Templates::
+* Scheme tutorial::
+* GNU Free Documentation License::
+* LilyPond index::
+@end menu
+
+@end ifnottex
+@c TOC - tex
+@contents
+@c INCLUDES
+@include learning/introduction.itely
+@include learning/common-notation.itely
+@include learning/fundamental.itely
+@include learning/tweaks.itely
+@include learning/templates.itely
+@include learning/scheme-tutorial.itely
+@include fdl.itexi
+@node LilyPond index
+@appendix LilyPond index
+
+@untranslated
+
+
+@bye
+
+@c -- SKELETON FILE --
--- /dev/null
+depth = ../../..
+
+LOCALSTEPMAKE_TEMPLATES = ly
+
+include $(depth)/make/stepmake.make
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c Don't replace quotes with directed quotes.
+@set txicodequoteundirected
+@set txicodequotebacktick
+@c ***** Displaying text *****
+@c We need this since @q{\} doesn't work with makeinfo 4.11 --
+@c say @q{@bs{}} instead.
+@c ***** Displaying images not generated by lilypond-book *****
+@c Current installation setup of Info docs requires that all images are
+@c expected to be found in the `lilypond/' subdirectory. `lilypond-book'
+@c already generates proper @image commands for images of music; these
+@c macro definitions do the same for other images.
+@c ***** Headers *****
+@c ***** Indexing *****
+@c Don't remove the `@c' within the macro definition! See section 19.3,
+@c `Macro Details and Caveats', in the texinfo info file for explanation.
+@c
+@c ***** Macros specific to translated docs *****
+@c ugh, cannot set/define global variable 'translationof' in any way :-(
+@set translationof \TEXT\
+@c ***** Macros specific to the web site *****
+@c keep the space for proper nesting of </p>
+@c not strictly necessary, but it makes things easier for updating news
+@c keep the space for proper nesting of </p>
+@c @image{\IMAGE-FILE\}
+@c @image{\IMAGE-FILE\}
+@c @image{\IMAGE-FILE\}
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Common notation
+@chapter Common notation
+
+@untranslated
+
+
+@ref{Introduction}.
+@menu
+* Single staff notation::
+* Multiple notes at once::
+* Songs::
+* Final touches::
+@end menu
+
+@node Single staff notation
+@section Single staff notation
+
+@untranslated
+
+
+@menu
+* Accidentals and key signatures::
+* Ties and slurs::
+* Articulation and dynamics::
+* Adding text::
+* Automatic and manual beams::
+* Advanced rhythmic commands::
+@end menu
+
+@node Accidentals and key signatures
+@subsection Accidentals and key signatures
+
+@untranslated
+
+
+@subheading Accidentals
+@c index accidentals
+@c index accidentals and key signatures
+@c index sharp
+@c index double sharp
+@c index sharp, double
+@c index flat
+@c index double flat
+@c index flat, double
+@c index key signature, setting
+@subheading Key signatures
+@c index key signature
+@c index major
+@c index minor
+@c index accidentals and key signature
+@c index content vs. layout
+@c index layout vs. content
+@subheading Warning: key signatures and pitches
+@c ode{is} and type @code{cis} and @code{fis} in the input file.
+@node Ties and slurs
+@subsection Ties and slurs
+
+@untranslated
+
+
+@c index tie
+@c index slur
+@c index slur, phrasing
+@c index phrasing slur
+@subheading Ties
+@subheading Slurs
+@c ode{)} respectively.
+@subheading Phrasing slurs
+@c ode{\(} and @code{\)}. You can have both @notation{slurs}
+@c index slurs versus ties
+@subheading Warnings: slurs vs. ties
+@node Articulation and dynamics
+@subsection Articulation and dynamics
+
+@untranslated
+
+
+@subheading Articulations
+@c index articulation
+@c index accent
+@c index staccato
+@subheading Fingerings
+@c index fingering
+@c ode{^} (up) or @code{_} (down). You can also use multiple
+@subheading Dynamics
+@c index dynamics
+@c index decrescendo
+@c index crescendo
+@c ode{\!} can be used:
+@node Adding text
+@subsection Adding text
+
+@untranslated
+
+
+@c index text, adding
+@c index adding text
+@c index markup
+@node Automatic and manual beams
+@subsection Automatic and manual beams
+
+@untranslated
+
+
+@c index beaming
+@c index automatic beams
+@c index manual beams
+@c index beams, automatic
+@c index beams, manual
+@c index beams, by hand
+@node Advanced rhythmic commands
+@subsection Advanced rhythmic commands
+
+@untranslated
+
+
+@subheading Partial measure
+@c index pickup
+@c index anacrusis
+@c index partial measure
+@c ode{\partial}. It is followed by a duration: @code{\partial 4}
+@subheading Tuplets
+@c index tuplets
+@c index triplets
+@subheading Grace notes
+@c index grace notes
+@c index acciaccatura
+@c index appoggiatura
+@node Multiple notes at once
+@section Multiple notes at once
+
+@untranslated
+
+
+@menu
+* Music expressions explained::
+* Multiple staves::
+* Staff groups::
+* Combining notes into chords::
+* Single staff polyphony::
+@end menu
+
+@node Music expressions explained
+@subsection Music expressions explained
+
+@untranslated
+
+
+@c index music expression
+@c index expression, music
+@c index compound music expression
+@c index music expression, compound
+@subheading Analogy: mathematical expressions
+@subheading Simultaneous music expressions: multiple staves
+@c index multiple staves
+@c index staves, multiple
+@c index polyphony
+@c index combining expressions in parallel
+@c index parallel expressions
+@c index expressions, parallel
+@c index relative notes and simultaneous music
+@c index relative notes and parallel expressions
+@c index simultaneous music and relative notes
+@c index parallel expressions and relative notes
+@c ode{@bs{}relative} command.}
+@subheading Simultaneous music expressions: single staff
+@node Multiple staves
+@subsection Multiple staves
+
+@untranslated
+
+
+@c index multiple staves
+@c index staves, multiple
+@c index context
+@c index context, notation
+@c index notation context
+@c ode{Staff} elements are then combined in parallel with @code{<<}
+@node Staff groups
+@subsection Staff groups
+
+@untranslated
+
+
+@c index piano staff
+@c index staff, piano
+@c index choir staff
+@c index staff, choir
+@c index grand staff
+@c index staff, grand
+@c index staff group
+@ref{Multiple staves}. However, now this entire expression is
+@node Combining notes into chords
+@subsection Combining notes into chords
+
+@untranslated
+
+
+@c index chords
+@c index note durations in chords
+@node Single staff polyphony
+@subsection Single staff polyphony
+
+@untranslated
+
+
+@c index polyphony
+@c index multiple voices
+@c index voices, more on one staff
+@c index single staff polyphony
+@c index spacer rest
+@c index rest, spacer
+@node Songs
+@section Songs
+
+@untranslated
+
+
+@menu
+* Setting simple songs::
+* Aligning lyrics to a melody::
+* Lyrics to multiple staves::
+@end menu
+
+@node Setting simple songs
+@subsection Setting simple songs
+
+@untranslated
+
+
+@c index lyrics
+@c index songs
+@node Aligning lyrics to a melody
+@subsection Aligning lyrics to a melody
+
+@untranslated
+
+
+@c index melisma
+@c index extender line
+@c index hyphens
+@c index underscore
+@c index lyrics, aligning
+@c index aligning lyrics
+@c index lyrics, multi-syllable words
+@c index words with multiple syllables in lyrics
+@c no ragged-right here because otherwise the hyphens get lost,
+@c but the example is long enough to avoid looking strange.
+@c no ragged-right here because otherwise the hyphens get lost,
+@c but the example is long enough to avoid looking strange.
+@node Lyrics to multiple staves
+@subsection Lyrics to multiple staves
+
+@untranslated
+
+
+@c index lyrics and multiple staves
+@c index multiple staves and lyrics
+@node Final touches
+@section Final touches
+
+@untranslated
+
+
+@menu
+* Organizing pieces with variables::
+* Version number::
+* Adding titles::
+* Absolute note names::
+* After the tutorial::
+@end menu
+
+@node Organizing pieces with variables
+@subsection Organizing pieces with variables
+
+@untranslated
+
+
+@c index variables
+@c index variables, defining
+@c index identifiers
+@c index macros
+@c index assigning variables
+@c index using variables
+@c index variables, using
+@c index variables, characters allowed in
+@c index characters allowed in variables
+@node Version number
+@subsection Version number
+
+@untranslated
+
+
+@c index versioning
+@c index version
+@c index version number
+@c index upgrades
+@c index future upgrades
+@c index updating files
+@c index files, updating
+@node Adding titles
+@subsection Adding titles
+
+@untranslated
+
+
+@c index title
+@c index headers
+@c index header block
+@node Absolute note names
+@subsection Absolute note names
+
+@untranslated
+
+
+@c index note names
+@c index note names, absolute
+@c index absolute mode
+@c index absolute values for pitches
+@c index pitches, absolute values
+@c index absolute note names
+@c ode{b} will always mean the note one step below middle C, and a
+@c ode{g,} will always mean the note on the bottom staff of the
+@node After the tutorial
+@subsection After the tutorial
+
+@untranslated
+
+
+@ref{Templates}. If you need any notation that was not covered in
+@ref{Extending the templates}.
+@c @ref{About the documentation}.
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node GNU Free Documentation License
+@appendix GNU Free Documentation License
+
+@untranslated
+
+
+@c index FDL, GNU Free Documentation License
+@c enter Version 1.1, March 2000
+@subheading ADDENDUM: How to use this License for your documents
+@c Local Variables:
+@c ispell-local-pdict: "ispell-dict"
+@c End:
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Fundamental concepts
+@chapter Fundamental concepts
+
+@untranslated
+
+
+@menu
+* How LilyPond input files work::
+* Voices contain music::
+* Contexts and engravers::
+* Extending the templates::
+@end menu
+
+@node How LilyPond input files work
+@section How LilyPond input files work
+
+@untranslated
+
+
+@menu
+* Introduction to the LilyPond file structure::
+* Score is a (single) compound musical expression::
+* Nesting music expressions::
+* On the un-nestedness of brackets and ties::
+@end menu
+
+@node Introduction to the LilyPond file structure
+@subsection Introduction to the LilyPond file structure
+
+@untranslated
+
+
+@c index input format
+@c index file structure
+@c index book
+@c index score
+@c ode{\score@{@}} command. This is because LilyPond automatically
+@c index implicit contexts
+@c index contexts, implicit
+@ref{Contexts and engravers}.
+@c ode{\score} command, leaving the others to default.
+@c index header
+@c index layout
+@c index midi
+@c ode{\midi} -- are special: unlike many other commands which begin
+@c ode{\header} is often placed above the @code{\score} command, as the
+@c ode{\layout @{ @}} and @code{\midi @{@}}. If these appear as
+@c index scores, multiple
+@c index book block, implicit
+@c index implicit book block
+@c ode{\book} command should be used to separate the different
+@c ode{\book} block.
+@c index layout block, effect of location
+@c ode{\book} block in which it appears -- i.e., a @code{\layout}
+@c index variables
+@c ode{melody} (everything after the equals sign) and inserts it
+@c ode{TimeKey},
+@c ode{pianorighthand}, or @code{foofoobarbaz}. For more details,
+@node Score is a (single) compound musical expression
+@subsection Score is a (single) compound musical expression
+
+@untranslated
+
+
+@c index score
+@c index contents of a score block
+@c index score block, contents of
+@c index compound music expression
+@c index music expression, compound
+@quotation
+@end quotation
+@ref{Music expressions explained}. In that section, we saw how to
+@c ode{StaffGroup} for this ensemble, which simply groups a number
+@c ode{\lyricmode}. These are essential to tell LilyPond
+@node Nesting music expressions
+@subsection Nesting music expressions
+
+@untranslated
+
+
+@c index staves, temporary
+@c index temporary staves
+@c index ossias
+@c index staff, positioning
+@node On the un-nestedness of brackets and ties
+@subsection On the un-nestedness of brackets and ties
+
+@untranslated
+
+
+@c index brackets, nesting
+@c index bracket types
+@c index brackets, enclosing vs. marking
+@c attempt to force this onto a new page
+@node Voices contain music
+@section Voices contain music
+
+@untranslated
+
+
+@menu
+* I'm hearing Voices::
+* Explicitly instantiating voices::
+* Voices and vocals::
+@end menu
+
+@node I'm hearing Voices
+@subsection I'm hearing Voices
+
+@untranslated
+
+
+@c index polyphony
+@c index layers
+@c index multiple voices
+@c index voices, multiple
+@c index Voice context
+@c index context, Voice
+@c index simultaneous music
+@c index music, simultaneous
+@c index concurrent music
+@c index music, concurrent
+@c index voices vs. chords
+@c index chords vs. voices
+@c ode{\\}, to place them in separate voices. Without these, the
+@c index voices, naming
+@c index voices crossing brackets
+@c index slurs crossing brackets
+@c index ties crossing brackest
+@ref{Using variables for tweaks}.
+@c index polyphony and relative note entry
+@c index relative note entry and polyphony
+@c ode{\relative @{ @}} block. Each note is still calculated
+@c ode{noteB} is relative to @code{noteA} @*
+@c ode{noteC} is relative to @code{noteB}, not @code{noteA}; @*
+@c ode{noteD} is relative to @code{noteB}, not @code{noteA} or
+@c ode{noteC}; @*
+@c ode{noteE} is relative to @code{noteD}, not @code{noteA}.
+@c The following should appear as music without code
+@c The following should appear as music without code
+@c The three voice styles should be defined in -init
+@c index stem down
+@c index voices and stem directions
+@c index stem directions and voices
+@c index stem up
+@node Explicitly instantiating voices
+@subsection Explicitly instantiating voices
+
+@untranslated
+
+
+@c index voice contexts, creating
+@c ode{\voiceOne} ... @code{\voiceFour} to indicate the required
+@c The following example should not display the code
+@c index voices, reverting to single
+@c index reverting to a single voice
+@c ode{\voiceFour} make them point downwards. These commands also
+@c ode{\oneVoice}, @code{\voiceOne} and @code{voiceTwo} have on
+@c index nesting music expressions
+@c index nesting simultaneous constructs
+@c index nesting voices
+@c index voices, temporary
+@c index voices, nesting
+@c index spacing notes
+@subsubheading Note columns
+@c index note column
+@c index note collisions
+@c index collisions, notes
+@c index shift commands
+@c ode{\shiftOff} commands specify the degree to which notes and
+@c ode{\shiftOnn} and @code{\shiftOnnn} define further shift
+@node Voices and vocals
+@subsection Voices and vocals
+
+@untranslated
+
+
+@c index Lyrics context, creating
+@c index lyrics, linking to voice
+@c index lyrics and beaming
+@c index beaming and lyrics
+@c ode{\autoBeamOff} to turn off the automatic beaming.
+@c index vocal score structure
+@c index choir staff
+@c ode{\lyricmode} to ensure they are interpreted as lyrics
+@c index hymn structure
+@c index SATB structure
+@c index vocal scores with multiple verses
+@c index multiple vocal verses
+@c index verses, multiple vocal
+@c index verse and refrain
+@c index book, example of using
+@c ode{\score} blocks within an implicit @code{\book} block, as
+@node Contexts and engravers
+@section Contexts and engravers
+
+@untranslated
+
+
+@menu
+* Contexts explained::
+* Creating contexts::
+* Engravers explained::
+* Modifying context properties::
+* Adding and removing engravers::
+@end menu
+
+@node Contexts explained
+@subsection Contexts explained
+
+@untranslated
+
+
+@c index contexts explained
+@quotation
+@end quotation
+@c ode{Score} and @code{Staff} contexts.
+@c ode{Voice} contexts there are contexts which fit between
+@c ode{PianoStaff} and @code{ChoirStaff} contexts. There
+@c ode{GregorianTranscriptionStaff}.
+@node Creating contexts
+@subsection Creating contexts
+
+@untranslated
+
+
+@c index new contexts
+@c index creating contexts
+@c index contexts, creating
+@c ode{Staff} contexts may be left to be created automatically, but for
+@c ode{Voice}). This command creates a new context, and starts
+@c ode{Staff} and @code{Voice} contexts in earlier sections, but
+@c index contexts, naming
+@c index naming contexts
+@c ode{Staff}, @code{Voice}, etc, and the identifying name of a
+@node Engravers explained
+@subsection Engravers explained
+
+@untranslated
+
+
+@c index engravers
+@c ode{Metronome_mark_engraver}, whose action and output apply to the
+@c ode{Score} context.
+@c The old Dynamic_engraver is deprecated. -jm
+@node Modifying context properties
+@subsection Modifying context properties
+
+@untranslated
+
+
+@c index context properties
+@c index context properties, modifying
+@c index modifying context properties
+@c ode{\set} command. This takes the form
+@c ode{Staff} or @code{Voice}. It may be omitted,
+@c attempt to force this onto a new page
+@c index properties operating in contexts
+@c index setting properties within contexts
+@c ode{instrumentName} clearly lives in the @code{Staff} context, since
+@c ode{\set} command set the property @code{instrumentName} in the
+@c ode{Voice} context to @qq{Alto}, but as LilyPond does not look
+@c ode{\set} or @code{\unset} again. Let's try changing the
+@c ode{##t} and @code{##f}, with two hash signs. A text property
+@subsubheading Setting context properties with @code{\with}
+@c index context properties, setting with \with
+@c ode{\with @{ .. @}} block in which the property values are
+@c ode{\set} and returned to their default value with @code{\unset}.
+@c index fontSize, default and setting
+@c ode{\unset fontSize} command.
+@subsubheading Setting context properties with @code{\context}
+@c index context properties, setting with \context
+@c ode{\with} block, introduced above. It is placed in a
+@c ode{\context} block within a @code{\layout} block. Each
+@c ode{\context} block will affect all contexts of the type specified
+@c ode{\layout} block appears. Here is a example to show the format:
+@c ode{\set} commands embedded in music statements.
+@c FIXME
+@c uncomment when backslash-node-name issue is resolved -pm
+@c @ruser{The set command}.
+@node Adding and removing engravers
+@subsection Adding and removing engravers
+
+@untranslated
+
+
+@c index engravers, adding
+@c index adding engravers
+@c index engravers, removing
+@c index removing engravers
+@subsubheading Changing a single context
+@c ode{\with} command placed immediately after the context creation
+@c index ambitus engraver
+@c ode{\consists @var{Engraver_name}},
+@c ode{Ambitus_engraver}, which is not normally included in any
+@c ode{Staff} context, it calculates the range from all
+@subsubheading Changing all contexts of the same type
+@c ode{\set} command in a @code{\context} block in the
+@node Extending the templates
+@section Extending the templates
+
+@untranslated
+
+
+@menu
+* Soprano and cello::
+* Four-part SATB vocal score::
+* Building a score from scratch::
+* Saving typing with variables and functions::
+* Scores and parts::
+@end menu
+
+@node Soprano and cello
+@subsection Soprano and cello
+
+@untranslated
+
+
+@c index template, modifying
+@c index modifying templates
+@c ode{melody} section. We don't want two @code{\score} sections
+@c ode{text} to be @code{sopranoLyrics}. Remember to rename both
+@c ode{melody = \relative c' @{ } part) and the name's use (in the
+@c ode{\score} section).
+@c ode{>>} around the music -- that tells LilyPond that there's
+@c Indentation in this example is deliberately poor
+@node Four-part SATB vocal score
+@subsection Four-part SATB vocal score
+
+@untranslated
+
+
+@c index template, SATB
+@c index SATB template
+@c The following should appear as music without code
+@c ode{\voiceXXX} commands should be removed. We also need to specify
+@node Building a score from scratch
+@subsection Building a score from scratch
+
+@untranslated
+
+
+@c index template, writing your own
+@c index example of writing a score
+@c index writing a score, example
+@c index score, example of writing
+@c ode{<< .. >>} for the manual two staff and the pedal organ staff,
+@c ode{@{ .. @}} in case your music is coded in several variables
+@c ode{\voiceOne} and @code{\voiceTwo}, and enter the time signature
+@node Saving typing with variables and functions
+@subsection Saving typing with variables and functions
+
+@untranslated
+
+
+@c index variables
+@c index variables
+@c TODO Avoid padtext - not needed with skylining
+@c TODO Replace the following with a better example -td
+@c Skylining handles this correctly without padText
+@c ode{padtext=}).
+@node Scores and parts
+@subsection Scores and parts
+
+@untranslated
+
+
+@c ode{\transpose f@tie{}c'} indicates that the argument, being
+@c ode{\hornNotes}, should be transposed by a fifth upwards. Sounding
+@c ode{f} is denoted by notated @code{c'}, which corresponds with the
+@c ode{Score} context to true (@code{##t}). Prepending the rest and
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Introduction
+@chapter Introduction
+
+@untranslated
+
+
+@menu
+* Compiling a file::
+* Advanced editors::
+* How to write input files::
+* How to read the manuals::
+@end menu
+
+@node Compiling a file
+@section Compiling a file
+
+@untranslated
+
+
+@menu
+* Entering input::
+* MacOS X::
+* Windows::
+* Command-line::
+@end menu
+
+@node Entering input
+@subsection Entering input
+
+@untranslated
+
+
+@c index compiling
+@c index first example
+@c index example, first
+@c index case sensitive
+@c in this case we don't want verbatim
+@subheading Entering music and viewing output
+@c index PDF file
+@c index viewing music
+@c index text editors
+@c index running LilyPond under MacOS X
+@c index MacOS X, running LilyPond
+@c index running LilyPond under Windows
+@c index Windows, running LilyPond
+@c index running LilyPond under Unix
+@c index Unix, running LilyPond
+@ref{Advanced editors}.
+@node MacOS X
+@subsection MacOS X
+
+@untranslated
+
+
+@node Windows
+@subsection Windows
+
+@untranslated
+
+
+@node Command-line
+@subsection Command-line
+
+@untranslated
+
+
+@node Advanced editors
+@section Advanced editors
+
+@untranslated
+
+
+@menu
+* Denemo::
+* LilyPondTool::
+* Emacs::
+* Vim::
+@end menu
+
+@node Denemo
+@subsection Denemo
+
+@untranslated
+
+
+@node LilyPondTool
+@subsection LilyPondTool
+
+@untranslated
+
+
+@node Emacs
+@subsection Emacs
+
+@untranslated
+
+
+@node Vim
+@subsection Vim
+
+@untranslated
+
+
+@node How to write input files
+@section How to write input files
+
+@untranslated
+
+
+@menu
+* Simple notation::
+* Working on input files::
+@end menu
+
+@node Simple notation
+@subsection Simple notation
+
+@untranslated
+
+
+@c index simple notation
+@c index notation, simple
+@subheading Pitches
+@c index pitches
+@c index relative mode
+@c index quote, single
+@c index comma
+@c index accidentals and relative mode
+@c index relative mode, and accidentals
+@c ode{c} is the closest C to middle C. This is followed by the
+@c ode{''} or @code{,,} -- but be careful that you use two single
+@c " - keeps quotes in order for context-sensitive editor -td
+@subheading Durations (rhythms)
+@c index note durations
+@c index durations
+@c index rhythms
+@c index whole note
+@c index half note
+@c index quarter note
+@c index dotted note
+@c index notating durations
+@subheading Rests
+@c index rest
+@c index notating rests
+@c ode{r}@tie{}:
+@subheading Time signature
+@c index time signature
+@subheading Clef
+@c index clef
+@c index treble
+@c index alto
+@c index tenor
+@c index bass
+@subheading All together
+@node Working on input files
+@subsection Working on input files
+
+@untranslated
+
+
+@c index curly braces
+@c index braces, curly
+@c index comments
+@c index line comment
+@c index comment, line
+@c index block comment
+@c index comment, line
+@c index case sensitive
+@c index whitespace insensitive
+@c index expressions
+@c ode{()} in mathematics. The braces should be surrounded by a
+@c index comments
+@c index line comment
+@c index block comment
+@c ode{%} introduces a line comment; anything after @code{%} on
+@node How to read the manuals
+@section How to read the manuals
+
+@untranslated
+
+
+@menu
+* Omitting braces::
+* Clickable examples::
+* Keyboard navigation::
+* Overview of manuals::
+@end menu
+
+@node Omitting braces
+@unnumberedsubsec Omitting braces
+
+@untranslated
+
+
+@c index how to read the manual
+@c index manual, reading
+@c index reading the manual
+@c index examples, clickable
+@c index clickable examples
+@c index tips for constructing files
+@c index templates
+@c index constructing files, tips
+@c index files, tips for constructing
+@c ode{@w{\relative c'' @{ ... @}}}, as we saw in @ref{Working on
+@c ode{@w{\relative c'' @{ @}}} like this:
+@c ode{\relative}! If we included @code{@w{\relative c'' @{ @}}}
+@node Clickable examples
+@unnumberedsubsec Clickable examples
+
+@untranslated
+
+
+@c no verbatim here
+@node Keyboard navigation
+@unnumberedsubsec Keyboard navigation
+
+@untranslated
+
+
+@node Overview of manuals
+@unnumberedsubsec Overview of manuals
+
+@untranslated
+
+
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: us-ascii; mode: texinfo; -*-
+@include version.itexi
+@include common-macros.itexi
+@c ***** Displaying text *****
+@c To get decent quotes in `foo' and ``foo''.
+@c artouche
+@quotation
+@quotation
+@c artouche
+@end quotation
+@end quotation
+@c ***** Headings in a doc subsection *****
+@c Don't insert an empty line after @predefined! Right now
+@c it doesn't matter, but a future implementation will probably
+@c add some code which needs this restriction.
+@subsubheading Predefined commands
+@c The next macro is a dummy currently since texinfo doesn't
+@c provide a real ragged-right environment yet.
+@c
+@c Due to a bug in texi2html (texi2html.pl CVS versions <= 1.245)
+@c the macro must not be empty.
+@c
+@subsubheading Selected Snippets
+@c Don't insert an empty line after @seealso! Otherwise we get
+@c unwanted extra vertical space in the PDF output.
+@subsubheading See also
+@subsubheading Known issues and warnings
+@c ***** Links and references *****
+@c Definitions for references:
+@c
+@c @rglos
+@c @rlearning
+@c @ruser
+@c @ressay
+@c @rprogram
+@c @rlsr
+@c @rinternals
+@c
+@c All these also have a @...named version which allows to specify the
+@c displayed text for the reference as second argument.
+@c
+@c ***** HTML + bigpage is a special case (other manual names); all other
+@c formats are treated similarly.
+@c *** not TeX ***
+@ifnottex
+@c ** bigpage **
+@ref{\TEXT\,,,music-glossary-big-page,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary-big-page,Music Glossary}
+@ref{\TEXT\,,,learning-big-page,Learning Manual}
+@ref{\TEXT\,,\DISPLAY\,learning-big-page,Learning Manual}
+@ref{\TEXT\,,,notation-big-page,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation-big-page,Notation Reference}
+@ref{\TEXT\,,,essay-big-page,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay-big-page,Essay}
+@ref{\TEXT\,,,application-big-page,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application-big-page,Application Usage}
+@ref{\TEXT\,,,snippets-big-page,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets-big-page,Snippets}
+@ref{\TEXT\,,,internals-big-page,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals-big-page,Internals Reference}
+@c ** not bigpage **
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,,notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation,Notation Reference}
+@ref{\TEXT\,,,essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@ref{\TEXT\,,,application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application,Application Usage}
+@ref{\TEXT\,,,snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets,Snippets}
+@ref{\TEXT\,,,internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals,Internals Reference}
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@ref{\TEXT\,,,lilypond-notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,lilypond-notation,Notation Reference}
+@ref{\TEXT\,,,lilypond-essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,lilypond-essay,Essay}
+@ref{\TEXT\,,,lilypond-application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,lilypond-application,Application Usage}
+@ref{\TEXT\,,,lilypond-snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,lilypond-snippets,Snippets}
+@ref{\TEXT\,,,lilypond-internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,lilypond-internals,Internals Reference}
+@end ifnottex
+@c *** TeX ***
+@c All commands below should work in the middle of the line;
+@c we thus must not use @vindex directly since it works only if placed
+@c on a line of its own. To overcome this problem, we define a
+@c replacement macro using the internal definition of @vindex which
+@c delimits arguments in the standard way (i.e., with braces).
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,\DISPLAY\,learning,Learning Manual}
+@ref{\TEXT\,,,notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation,Notation Reference}
+@ref{\TEXT\,,,essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@ref{\TEXT\,,,application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application,Application Usage}
+@ref{\TEXT\,,,snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets,Snippets}
+@ref{\TEXT\,,,internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals,Internals Reference}
+@c ***** Macros specific to the web site *****
+@c LEGALESE
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Scheme tutorial
+@appendix Scheme tutorial
+
+@untranslated
+
+
+@c index Scheme
+@c index GUILE
+@c index Scheme, in-line code
+@c index accessing Scheme
+@c index evaluating Scheme
+@c index LISP
+@c ode{GUILE_LOAD_PATH} to the directory @code{../usr/shr/guile/1.8}
+@c ode{1} is the (integer) number one, while @code{-1.5} is a
+@c ode{#} symbols to introduce a Scheme section are not required.
+@c ode{(* 3 4)} is replaced by its value @code{12}. A similar thing
+@c index quoting in Scheme
+@c ode{24} for the @code{twentyFour}. Instead, we get the name
+@c ode{twentyFour}.
+@c ode{twentyFour} in the example above) and variables of internal
+@c index properties vs. variables
+@c index variables vs. properties
+@menu
+* Tweaking with Scheme::
+@end menu
+
+@node Tweaking with Scheme
+@appendixsec Tweaking with Scheme
+
+@untranslated
+
+
+@c ode{\override TextScript #'extra-offset = ( 1 . -1)}. But
+@c This isn't a valid example with skylining
+@c It works fine without padText -td
+@c Check this is a valid example with skylining
+@c It is - 'padding still works
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Templates
+@appendix Templates
+
+@untranslated
+
+
+@c bad node name for ancient notation to avoid conflict
+@menu
+* Single staff::
+* Piano templates::
+* String quartet::
+* Vocal ensembles::
+* Orchestral templates::
+* Ancient notation templates::
+* Jazz combo::
+* lilypond-book templates::
+@end menu
+
+@node Single staff
+@appendixsec Single staff
+
+@untranslated
+
+
+@appendixsubsec Notes only
+@appendixsubsec Notes and lyrics
+@appendixsubsec Notes and chords
+@appendixsubsec Notes, lyrics, and chords.
+@node Piano templates
+@appendixsec Piano templates
+
+@untranslated
+
+
+@appendixsubsec Solo piano
+@appendixsubsec Piano and melody with lyrics
+@appendixsubsec Piano centered lyrics
+@appendixsubsec Piano centered dynamics
+@node String quartet
+@appendixsec String quartet
+
+@untranslated
+
+
+@appendixsubsec String quartet
+@appendixsubsec String quartet parts
+@node Vocal ensembles
+@appendixsec Vocal ensembles
+
+@untranslated
+
+
+@appendixsubsec SATB vocal score
+@appendixsubsec SATB vocal score and automatic piano reduction
+@appendixsubsec SATB with aligned contexts
+@node Orchestral templates
+@appendixsec Orchestral templates
+
+@untranslated
+
+
+@appendixsubsec Orchestra, choir and piano
+@c bad node name to avoid node name conflict
+@node Ancient notation templates
+@appendixsec Ancient notation templates
+
+@untranslated
+
+
+@appendixsubsec Transcription of mensural music
+@appendixsubsec Gregorian transcription template
+@node Jazz combo
+@appendixsec Jazz combo
+
+@untranslated
+
+
+@node lilypond-book templates
+@appendixsec lilypond-book templates
+
+@untranslated
+
+
+@appendixsubsec LaTeX
+@appendixsubsec Texinfo
+@appendixsubsec xelatex
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of learning.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Tweaking output
+@chapter Tweaking output
+
+@untranslated
+
+
+@menu
+* Tweaking basics::
+* The Internals Reference manual::
+* Appearance of objects::
+* Placement of objects::
+* Collisions of objects::
+* Further tweaking::
+@end menu
+
+@node Tweaking basics
+@section Tweaking basics
+
+@untranslated
+
+
+@menu
+* Introduction to tweaks::
+* Objects and interfaces::
+* Naming conventions of objects and properties::
+* Tweaking methods::
+@end menu
+
+@node Introduction to tweaks
+@subsection Introduction to tweaks
+
+@untranslated
+
+
+@ref{Contexts and engravers}, as Contexts, Engravers, and the
+@node Objects and interfaces
+@subsection Objects and interfaces
+
+@untranslated
+
+
+@c index object
+@c index grob
+@c index spanner
+@c index interface
+@c index properties, object
+@c index object properties
+@c index layout object
+@c index object, layout
+@c index interface
+@c ode{Lyrics} objects, as well as objects to represent all
+@node Naming conventions of objects and properties
+@subsection Naming conventions of objects and properties
+
+@untranslated
+
+
+@c index naming conventions for objects
+@c index naming conventions for properties
+@c index objects, naming conventions
+@c index properties, naming conventions
+@ref{Contexts and engravers}. Here for reference is a list
+@node Tweaking methods
+@subsection Tweaking methods
+
+@untranslated
+
+
+@c index tweaking methods
+@c index override command
+@c index override syntax
+@ref{Adding and removing engravers}. We must now introduce some more
+@c ode{\override}. Because this command has to modify
+@c ode{Lyrics}, and we shall omit it in many of the following
+@c index color property, example
+@c index NoteHead, example of overriding
+@c index revert command
+@c index color property, example
+@c index NoteHead, example of overriding
+@c ode{\override} or @code{\set} command to be effective only
+@c index color property, example
+@c index NoteHead, example of overriding
+@c index overrideProperty command
+@c ode{\overrideProperty}, which is occasionally required.
+@c Maybe explain in a later iteration -td
+@c index tweak command
+@c ode{\once \override} would do:
+@c index font-size property, example
+@c index NoteHead, example of overriding
+@c index font-size property, example
+@c index @code{\tweak}, example
+@c ode{\tweak} command is simply
+@c index color property, example
+@c index @code{\tweak}, example
+@c index tuplets, nested
+@c index triplets, nested
+@c index bracket, tuplet
+@c index bracket, triplet
+@c index tuplet bracket
+@c index triplet bracket
+@c index @code{\tweak}, example
+@c index direction property, example
+@c index color property, example
+@c ode{\override} commands:
+@c index text property, example
+@c index tuplet-number function, example
+@c index transparent property, example
+@c index TupletNumber, example of overriding
+@c NOTE Tuplet brackets collide if notes are high on staff
+@c See issue 509
+@node The Internals Reference manual
+@section The Internals Reference manual
+
+@untranslated
+
+
+@c index Internals Reference
+@menu
+* Properties of layout objects::
+* Properties found in interfaces::
+* Types of properties::
+@end menu
+
+@node Properties of layout objects
+@subsection Properties of layout objects
+
+@untranslated
+
+
+@c index properties of layout objects
+@c index properties of grobs
+@c index grobs, properties of
+@c index layout objects, properties of
+@c index Internals Reference manual
+@c ode{\override} command would be needed. But is there a
+@c index override example
+@c index Internals Reference, example of using
+@c index @code{\addlyrics} example
+@c ode{thickness} (number)
+@c ode{thickness} and that the new value should be a number
+@c index Slur example of overriding
+@c index thickness property, example
+@subheading Finding the context
+@c index context, finding
+@c index context, identifying correct
+@c ode{Slur_engraver} page. At the very bottom it tells
+@subheading Overriding once only
+@c index overriding once only
+@c index once override
+@c index Slur, example of overriding
+@c index thickness property, example
+@subheading Reverting
+@c index revert
+@c index default properties, reverting to
+@c ode{\once} placed immediately before each of the notes where
+@c index Slur, example of overriding
+@c index thickness property, example
+@c index Slur, example of overriding
+@c index thickness property, example
+@node Properties found in interfaces
+@subsection Properties found in interfaces
+
+@untranslated
+
+
+@c index interface
+@c index interface properties
+@c index properties in interfaces
+@c ode{\override} command do we need to do this? We first look in the
+@c ode{font-interface}.
+@c ode{font-interface} but @code{font-shape} is not? The answer is
+@c ode{font-shape} is not. The entries in @code{LyricText} then tell
+@c ode{LyricText}. Other objects which support @code{font-interface}
+@c ode{italic}. As before, we'll omit the context.
+@c ode{thickness} or @code{font-shape}, others are used as values that
+@c index font-shape property, example
+@c index italic, example
+@c index LyricText, example of overriding
+@c index @code{\addlyrics}, example
+@subheading Specifying the context in lyric mode
+@c index context, specifying in lyric mode
+@c index lyric mode, specifying context
+@node Types of properties
+@subsection Types of properties
+
+@untranslated
+
+
+@c index property types
+@c ode{symbol}. To be valid, the value given to a property
+@c ode{\override} command.
+@node Appearance of objects
+@section Appearance of objects
+
+@untranslated
+
+
+@menu
+* Visibility and color of objects::
+* Size of objects::
+* Length and thickness of objects::
+@end menu
+
+@node Visibility and color of objects
+@subsection Visibility and color of objects
+
+@untranslated
+
+
+@c ode{BarLine}. Its properties include two that control its
+@subheading stencil
+@c index stencil property
+@c index BarLine, example of overriding
+@c index stencil property, example
+@c index BarLine, example of overriding
+@c index stencil property, example
+@c ode{stencil} property of the @code{NoteHead} object is set to
+@c ode{#f}. If this is the case, you can instead use the
+@c ode{point-stencil} function, which sets the stencil to a object
+@subheading break-visibility
+@c index break-visibility property
+@c ode{break-visibility} property requires a vector of three booleans.
+@c ode{\override} command.
+@c index BarLine, example of overriding
+@c index break-visibility property, example
+@subheading transparent
+@c index transparent property
+@c index transparency
+@c ode{grob-interface}. So the command to make the time signature
+@c index TimeSignature, example of overriding
+@c index transparent property, example
+@c index TimeSignature, example of overriding
+@c index stencil property, example
+@subheading color
+@c index color property
+@c index BarLine, example of overriding
+@c index color property, example
+@c index color, X11
+@c index X11 colors
+@c ode{x11-color}, like this:
+@c index BarLine, example of overriding
+@c index color property, example
+@c index rgb colors
+@c index color, rgb
+@c index BarLine, example of overriding
+@c index color property, example
+@c index StaffSymbol, example of overriding
+@c index TimeSignature, example of overriding
+@c index Clef, example of overriding
+@c index NoteHead, example of overriding
+@c index Stem, example of overriding
+@c index BarLine, example of overriding
+@c index color property, example
+@c index x11-color, example of using
+@node Size of objects
+@subsection Size of objects
+
+@untranslated
+
+
+@c index changing size of objects
+@c index size of objects
+@c index objects, size of
+@c index objects, changing size of
+@c index alignAboveContext property, example
+@c index @code{\with}, example
+@c index alignAboveContext property, example
+@c index @code{\with}, example
+@c index stencil property, example
+@c index Clef, example of overriding
+@c index TimeSignature, example of overriding
+@c ode{\set} or @code{\override} commands embedded in the
+@c ode{\with} clause, or if none have been set there, the normal
+@c ode{alignBelowContext}, are two such properties -- once the staff
+@c index alignAboveContext property, example
+@c index @code{\with}, example
+@c index Clef, example of overriding
+@c index TimeSignature, example of overriding
+@c index alignAboveContext property, example
+@c index @code{\with}, example
+@c index Clef, example of overriding
+@c index TimeSignature, example of overriding
+@c index fontSize property, example
+@node Length and thickness of objects
+@subsection Length and thickness of objects
+
+@untranslated
+
+
+@c index distances
+@c index thickness
+@c index length
+@c index magstep
+@c index size, changing
+@c index stem length, changing
+@c index staff line spacing, changing
+@c ode{line-thickness.} For example, by default, the lines of
+@c ode{magstep} provided for exactly this purpose. It takes
+@c index alignAboveContext property, example
+@c index @code{\with}, example
+@c index Clef, example of overriding
+@c index TimeSignature, example of overriding
+@c index fontSize property, example
+@c index StaffSymbol, example of overriding
+@c index magstep function, example of using
+@c index staff-space property, example
+@c index stencil property, example
+@c ode{thickness} property. An example of changing the thickness
+@node Placement of objects
+@section Placement of objects
+
+@untranslated
+
+
+@menu
+* Automatic behavior::
+* Within-staff objects::
+* Outside-staff objects::
+@end menu
+
+@node Automatic behavior
+@subsection Automatic behavior
+
+@untranslated
+
+
+@c index within-staff objects
+@c index outside-staff objects
+@c index objects, within-staff
+@c index objects, outside-staff
+@c ode{outside-staff-priority} property to determine the order in
+@c ode{outside-staff-priority}. The outside-staff objects are
+@c ode{outside-staff-priority}, and placed so that they do not
+@c ode{outside-staff-priority} the one encountered first will be
+@c index markup example
+@node Within-staff objects
+@subsection Within-staff objects
+
+@untranslated
+
+
+@c index down
+@c index up
+@c index center
+@c index neutral
+@c index Stem, example of overriding
+@c index direction property, example
+@c ode{UP} for stems, but for some objects it means @q{center}.
+@c ode{\once \override} command or use the predefined command
+@c ode{\xxxNeutral} command.
+@subheading Fingering
+@c index fingering, placement
+@c index fingering, chords
+@c index Fingering, example of overriding
+@c index direction property, example
+@c index fingering example
+@c index fingering example
+@c index fingering example
+@c ode{\set fingeringOrientations} command. The format of this
+@c ode{\set fingeringOrientations = #'([up] [left/right] [down])}
+@c ode{\set} is used because @code{fingeringOrientations} is a
+@c ode{New_fingering_engraver}.
+@c ode{up} appears in the list), below (if @code{down} appears),
+@c ode{right} are mutually exclusive -- fingering may be placed
+@c index fingering example
+@c index @code{\set}, example of using
+@c index fingeringOrientations property, example
+@c ode{Fingering} object in the IR to be @code{-5}, so let's
+@node Outside-staff objects
+@subsection Outside-staff objects
+
+@untranslated
+
+
+@c ode{grob-interface} and so is a property of all layout objects.
+@c ode{Staff} or @code{Voice} contexts.
+@c index text spanner
+@c index ottava bracket
+@c index TextSpanner, example of overriding
+@c index bound-details property, example
+@c index tweaking bar number placement
+@c index bar numbers, tweaking placement
+@c index tweaking metronome mark placement
+@c index metronome mark, tweaking placement
+@c index tweaking rehearsal mark placement
+@c index rehearsal marks, tweaking placement
+@c ode{Bar_number_engraver}, @code{Metronome_mark_engraver} or
+@c ode{Mark_engraver} respectively should be removed from the
+@c ode{Score} context and placed in the top @code{Staff} context. If
+@c ode{outside-staff-priority} values:
+@c ode{TextSpanner}, remembering that @code{OttavaBracket} is created
+@c index TextSpanner, example of overriding
+@c index bound-details property, example
+@c index slurs and outside-staff-priority
+@c index slurs and articulations
+@c index articulations and slurs
+@c index TextScript, example of overriding
+@c index outside-staff-priority property, example
+@subheading \textLengthOn
+@c index notes, spreading out with text
+@c ode{\textLengthOff}. Remember @code{\once} only works with
+@c ode{\override}, @code{\set}, @code{\revert} or @code{unset},
+@c index markup text, allowing collisions
+@c index TextScript, example of overriding
+@c index outside-staff-priority property, example
+@subheading Dynamics
+@c index tweaking dynamics placement
+@c index dynamics, tweaking placement
+@subheading Grob sizing
+@c index grob sizing
+@c index sizing grobs
+@c ode{grob-interface}.
+@c index @code{extra-spacing-width}
+@c ode{extra-spacing-width} to @code{'(+inf.0 . -inf.0)}. So
+@c ode{'(0 . 0)} so the true width shines through. This is
+@c index DynamicText, example of overriding
+@c index extra-spacing-width property, example
+@c index DynamicText, example of overriding
+@c index extra-spacing-width property, example
+@c ode{staff-padding} which is covered in the following section.
+@node Collisions of objects
+@section Collisions of objects
+
+@untranslated
+
+
+@menu
+* Moving objects::
+* Fixing overlapping notation::
+* Real music example::
+@end menu
+
+@node Moving objects
+@subsection Moving objects
+
+@untranslated
+
+
+@c index moving overlapping objects
+@c index moving colliding objects
+@c index moving colliding grobs
+@c index objects, moving colliding
+@c index grobs, moving colliding
+@c ode{direction}
+@ref{Within-staff objects}.
+@c ode{padding}, @code{left-padding},
+@c ode{right-padding}, @code{staff-padding}
+@c index padding
+@c index left-padding property
+@c index padding property
+@c index right-padding property
+@c index staff-padding property
+@c ode{side-position-interface}.
+@c ode{AccidentalPlacement} object has any effect on the placement
+@c ode{padding} property: @code{padding} controls the minimum amount of
+@c ode{side-position-interface} and the nearest other object (generally
+@c ode{self-alignment-X}
+@c index self-alignment-X property
+@c ode{-1} and @code{+1} may be specified, where @code{-1} is
+@c ode{extra-spacing-width}
+@c index extra-spacing-width property
+@c ode{item-interface}. It takes two numbers, the first is added
+@c ode{staff-position}
+@c index staff-position property
+@c ode{staff-position} is a property of the
+@c ode{staff-symbol-referencer-interface}, which is supported by
+@c ode{force-hshift}
+@c index force-hshift property
+@ref{Explicitly instantiating voices}) do not resolve the note
+@c index extra-offset property
+@c ode{grob-interface}. It takes a pair of numbers which specify the
+@c index positions property
+@node Fixing overlapping notation
+@subsection Fixing overlapping notation
+
+@untranslated
+
+
+@subheading padding property
+@c index padding
+@c index fixing overlapping notation
+@c index overlapping notation
+@c index Script, example of overriding
+@c index padding property, example
+@c index MetronomeMark, example of overriding
+@c index padding property, example
+@c ode{Voice} context will not be noticed. For more details, see
+@subheading left-padding and right-padding
+@c index left-padding property
+@c index right-padding property
+@c index Accidental, example of overriding
+@c index text property, example
+@c index stencil property, example
+@c index AccidentalPlacement, example of overriding
+@c index right-padding property, example
+@subheading staff-padding property
+@c index aligning objects on a baseline
+@c index objects, aligning on a baseline
+@c ode{staff-padding} can be used to align objects such as dynamics
+@c ode{DynamicLineSpanner}. This is because the baseline should apply
+@c index DynamicText, example of overriding
+@c index extra-spacing-width property, example
+@c index DynamicLineSpanner, example of overriding
+@c index staff-padding property, example
+@subheading self-alignment-X property
+@c index StringNumber, example of overriding
+@c index self-alignment-X property, example
+@subheading staff-position property
+@c index object collision within a staff
+@c ode{staff-position} is set to -4 for MultiMeasureRest, so we need to
+@c index MultiMeasureRest, example of overriding
+@c index staff-position property, example
+@subheading extra-offset property
+@c index positioning objects
+@c index positioning grobs
+@c index objects, positioning
+@c index grobs, positioning
+@c index Fingering, example of overriding
+@c index extra-offset property, example
+@subheading positions property
+@c index controlling tuplets, slurs, phrasing slurs, and beams manually
+@c index manually controlling tuplets, slurs, phrasing slurs, and beams
+@c index tuplet beams, controlling manually
+@c index slurs, controlling manually
+@c index phrasing slurs, controlling manually
+@c index beams, controlling manually
+@c index PhrasingSlur, example of overriding
+@c index positions property, example
+@c index Beam, example of overriding
+@c index positions property, example
+@subheading force-hshift property
+@c FIXME: formatting stuff (ie not important right now IMO)
+@c @a nchor Chopin finally corrected TODOgp
+@c index NoteColumn, example of overriding
+@c index force-hshift property, example
+@node Real music example
+@subsection Real music example
+
+@untranslated
+
+
+@c The following should appear as music without code
+@c This example should not be indexed
+@c ode{staff-position} property, which is specified in half staff
+@c ode{\once \override Tie #'staff-position = #3.5}
+@c index Tie, example of overriding
+@c index staff-position property, example
+@c index NoteColumn, example of overriding
+@c index force-hshift property, example
+@c index Stem, example of overriding
+@c index transparent property, example
+@node Further tweaking
+@section Further tweaking
+
+@untranslated
+
+
+@menu
+* Other uses for tweaks::
+* Using variables for tweaks::
+* Style sheets::
+* Other sources of information::
+* Avoiding tweaks with slower processing::
+* Advanced tweaks with Scheme::
+@end menu
+
+@node Other uses for tweaks
+@subsection Other uses for tweaks
+
+@untranslated
+
+
+@c index transparent property, use of
+@c index objects, making invisible
+@c index removing objects
+@c index objects, removing
+@c index hiding objects
+@c index objects, hiding
+@c index invisible objects
+@c index objects, invisible
+@c index tying notes across voices
+@subheading Tying notes across voices
+@c index Stem, example of overriding
+@c index transparent property, example
+@c ode{length} to @code{8},
+@subheading Simulating a fermata in MIDI
+@c index stencil property, use of
+@c index fermata, implementing in MIDI
+@c index MetronomeMark, example of overriding
+@c index transparent property, example
+@c index MetronomeMark, example of overriding
+@c index stencil property, example
+@node Using variables for tweaks
+@subsection Using variables for tweaks
+
+@untranslated
+
+
+@c index variables, using for tweaks
+@c index using variables for tweaks
+@c index tweaks, using variables for
+@c ode{\override Lyrics . LyricText #'font-shape = #'italic}
+@c ode{\override Lyrics . LyricText #'font-series = #'bold}
+@c ode{\revert Lyrics . LyricText #'font-shape}
+@c ode{\revert Lyrics . LyricText #'font-series}
+@c index LyricText, example of overriding
+@c index font-shape property, example
+@c index font-series property, example
+@node Style sheets
+@subsection Style sheets
+
+@untranslated
+
+
+@ref{Tweaking output}, for details. But what if you have many
+@ref{Advanced tweaks with Scheme}.
+@c We have to do this awkward example/lilypond-non-verbatim
+@c because we can't do the \include stuff in the manual.
+@c ode{\include "definitions.ily"} with
+@c ode{\include "web-publish.ily"}. Of course, we could make this
+@node Other sources of information
+@subsection Other sources of information
+
+@untranslated
+
+
+@node Avoiding tweaks with slower processing
+@subsection Avoiding tweaks with slower processing
+
+@untranslated
+
+
+@node Advanced tweaks with Scheme
+@subsection Advanced tweaks with Scheme
+
+@untranslated
+
+
+@c ode{\tweak} commands, an even more powerful way of modifying
+@c index x11-color function, example of using
+@c index NoteHead, example of overriding
+@c index color property, setting to Scheme procedure
+
+@c -- SKELETON FILE --
--- /dev/null
+@c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+ Translation of GIT committish: 8135382760aa0adfac5aed987a272c394e59dbdb
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@include version.itexi
+@include common-macros.itexi
+
+
+@c ***** Displaying text *****
+
+@c To get decent quotes in `foo' and ``foo''.
+@c FIXME: Use thin spaces for @qq.
+
+@ifnotinfo
+
+@macro q{TEXT}
+@quoteleft{}\TEXT\@quoteright{}
+@end macro
+
+@macro qq{TEXT}
+@guillemetleft{}@tie{}\TEXT\@tie{}@guillemetright{}
+@end macro
+
+@end ifnotinfo
+
+@ifinfo
+
+@macro q{TEXT}
+`\TEXT\'
+@end macro
+
+@macro qq{TEXT}
+« \TEXT\ »
+@end macro
+
+@end ifinfo
+
+
+@ifhtml
+
+@macro warning{TEXT}
+@cartouche
+@b{Note :} \TEXT\
+@end cartouche
+@end macro
+
+@end ifhtml
+
+@ifnothtml
+
+@macro warning{TEXT}
+@quotation
+@quotation
+@cartouche
+@b{Note :} \TEXT\
+@end cartouche
+@end quotation
+@end quotation
+@end macro
+
+@end ifnothtml
+
+
+
+@c ***** Headings in a doc subsection *****
+
+@c Don't insert an empty line after @predefined! Right now
+@c it doesn't matter, but a future implementation will probably
+@c add some code which needs this restriction.
+
+@macro predefined
+@noindent
+@subsubheading Commandes prédéfinies
+@end macro
+
+@c The next macro is a dummy currently since texinfo doesn't
+@c provide a real ragged-right environment yet.
+@c
+@c Due to a bug in texi2html (texi2html.pl CVS versions <= 1.245)
+@c the macro must not be empty.
+
+@macro endpredefined
+@c
+@end macro
+
+
+@macro snippets
+@noindent
+@subsubheading Morceaux choisis
+@end macro
+
+
+@c obsolete, remove when translation is fully updated
+@macro commonprop
+@noindent
+@subsubheading Propriétés couramment modifiées
+@end macro
+
+
+@c Don't insert an empty line after @seealso! Otherwise we get
+@c unwanted extra vertical space in the PDF output.
+
+@macro seealso
+@noindent
+@subsubheading Voir aussi
+@indent
+@end macro
+
+
+@macro knownissues
+@noindent
+@subsubheading Problèmes connus et avertissements
+@end macro
+
+
+
+
+@c ***** Links and references *****
+
+@c Definitions for references:
+@c
+@c @rglos
+@c @rlearning
+@c @ruser
+@c @rprogram
+@c @rlsr
+@c @rinternals
+@c
+@c All these also have a @...named version which allows to specify the
+@c displayed text for the reference as second argument.
+@c
+@c ***** HTML + bigpage is a special case (other manual names); all other
+@c formats are treated similarly.
+
+
+@c *** not TeX ***
+
+@ifnottex
+
+@c ** bigpage **
+
+@ifset bigpage
+
+@macro rglos{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,music-glossary-big-page,Glossaire}
+@end macro
+
+@macro rglosnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,music-glossary-big-page,Glossaire}
+@end macro
+
+@macro rlearning{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,learning-big-page,Manuel d'initiation}
+@end macro
+
+@macro rlearningnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,learning-big-page,Manuel d'initiation}
+@end macro
+
+@macro ruser{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,notation-big-page,Manuel de notation}
+@end macro
+
+@macro rusernamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,notation-big-page,Manuel de notation}
+@end macro
+
+@macro ressay{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,essay-big-page,Essay}
+@end macro
+
+@macro ressaynamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,essay-big-page,Essay}
+@end macro
+
+@macro rprogram{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,application-big-page,Manuel d'utilisation du programme}
+@end macro
+
+@macro rprogramnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,application-big-page,Manuel d'utilisation du programme}
+@end macro
+
+@macro rlsr{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,snippets-big-page,Exemples de code}
+@end macro
+
+@macro rlsrnamed{TEXT,DISPLAY}
+@ref{\TEXT\,,\DISPLAY\,snippets-big-page,Exemples de code}
+@end macro
+
+@macro rinternals{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,internals-big-page,Référence des propriétés internes}
+@end macro
+
+@macro rinternalsnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,,internals-big-page,Référence des propriétés internes}
+@end macro
+
+@end ifset
+
+
+@c ** not bigpage **
+
+@ifclear bigpage
+
+@macro rglos{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,music-glossary,Glossaire}
+@end macro
+
+@macro rglosnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Glossaire}
+@end macro
+
+@macro rlearning{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,learning,Manuel d'initiation}
+@end macro
+
+@macro rlearningnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,learning,Manuel d'initiation}
+@end macro
+
+@macro ruser{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,notation,Manuel de notation}
+@end macro
+
+@macro rusernamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,notation,Manuel de notation}
+@end macro
+
+@macro ressay{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,essay,Essay}
+@end macro
+
+@macro ressaynamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@end macro
+
+@macro rprogram{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,application,Manuel d'utilisation du programme}
+@end macro
+
+@macro rprogramnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,application,Manuel d'utilisation du programme}
+@end macro
+
+@macro rlsr{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,snippets,Exemples de code}
+@end macro
+
+@macro rlsrnamed{TEXT,DISPLAY}
+@ref{\TEXT\,,\DISPLAY\,snippets,Exemples de code}
+@end macro
+
+@macro rinternals{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,internals,Référence des propriétés internes}
+@end macro
+
+@macro rinternalsnamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,,internals,Référence des propriétés internes}
+@end macro
+
+@end ifclear
+
+@end ifnottex
+
+
+@c *** TeX ***
+
+@iftex
+
+@c All commands below should work in the middle of the line;
+@c we thus must not use @vindex directly since it works only if placed
+@c on a line of its own. To overcome this problem, we define a
+@c replacement macro using the internal definition of @vindex which
+@c delimits arguments in the standard way (i.e., with braces).
+
+@tex
+\gdef\lilyvindex#1{\doind{vr}{\code #1}\ignorespaces}
+@end tex
+
+@macro rglos{TEXT}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,,music-glossary,Glossaire}
+@end macro
+
+@macro rglosnamed{TEXT,DISPLAY}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Glossaire}
+@end macro
+
+@macro rlearning{TEXT}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,,learning.fr,Manuel d'initiation}
+@end macro
+
+@macro rlearningnamed{TEXT,DISPLAY}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,\DISPLAY\,learning.fr,Manuel d'initiation}
+@end macro
+
+@macro ruser{TEXT}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,,notation.fr,Manuel de notation}
+@end macro
+
+@macro rusernamed{TEXT,DISPLAY}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,\DISPLAY\,notation.fr,Manuel de notation}
+@end macro
+
+@macro ressay{TEXT}
+@vindex \TEXT\
+@ref{\TEXT\,,,lilypond-essay,Essay}
+@end macro
+
+@macro ressaynamed{TEXT,DISPLAY}
+@vindex \TEXT\
+@ref{\TEXT\,,\DISPLAY\,lilypond-essay,Essay}
+@end macro
+
+@macro rprogram{TEXT}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,,application.fr,Manuel d'utilisation du programme}
+@end macro
+
+@macro rprogramnamed{TEXT,DISPLAY}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,\DISPLAY\,application.fr,Manuel d'utilisation du programme}
+@end macro
+
+@macro rlsr{TEXT}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,,snippets,Exemples de code}
+@end macro
+
+@macro rlsrnamed{TEXT,DISPLAY}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,\DISPLAY\,snippets,Exemples de code}
+@end macro
+
+@macro rinternals{TEXT}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,,internals,Référence des propriétés internes}
+@end macro
+
+@macro rinternalsnamed{TEXT,DISPLAY}
+@lilyvindex{\TEXT\}
+@ref{\TEXT\,,,internals,Référence des propriétés internes}
+@end macro
+
+@end iftex
+
+
+@c ***** Macros specific to translated docs *****
+
+@macro englishref
+Cette section n'est pas encore encore traduite, veuillez
+vous reporter à la documentation correspondante en anglais.
+@end macro
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@setfilename lilypond-notation.info
+@settitle GNU LilyPond Notation Reference
+@documentencoding UTF-8
+@documentlanguage en
+@include macros.itexi
+@afourpaper
+@c Keep this here, since it pertains to the direntry below.
+@c * lilypond: (lilypond-application)Running LilyPond. Invoking the
+@c LilyPond program.
+@c
+@c Info files are no longer installed in a subdirectory, images are
+@c expected to be found in lilypond/ subdirectory.
+@c don't remove this comment.
+@ifnottex
+@node Top
+@top GNU LilyPond --- Notation Reference
+
+@untranslated
+
+
+@chapheading The music typesetter
+@c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX.
+@end ifnottex
+@c This produces the unified index
+@finalout
+@titlepage
+@title LilyPond
+@subtitle The music typesetter
+@titlefont{Notation Reference}
+@author The LilyPond development team
+@quotation
+@end quotation
+@vskip 20pt
+@end titlepage
+@copying
+@quotation
+@end quotation
+@end copying
+@ifnottex
+@quotation
+@end quotation
+@end ifnottex
+@ifnottex
+@c @rlearning{About the documentation}.
+@c index web site
+@c index URL
+@include dedication.itely
+@menu
+* Musical notation::
+* Specialist notation::
+* General input and output::
+* Spacing issues::
+* Changing defaults::
+* Interfaces for programmers::
+* Notation manual tables::
+* Cheat sheet::
+* LilyPond grammar::
+* GNU Free Documentation License::
+* LilyPond command index::
+* LilyPond index::
+@end menu
+
+@end ifnottex
+@c * Literature list:: Reference works about music notation.
+@contents
+@include notation/notation.itely
+@include notation/specialist.itely
+@include notation/input.itely
+@include notation/spacing.itely
+@include notation/changing-defaults.itely
+@include notation/programming-interface.itely
+@c @include notation/literature.itely
+@include notation/notation-appendices.itely
+@include notation/cheatsheet.itely
+@node LilyPond grammar
+@appendix LilyPond grammar
+
+@untranslated
+
+
+@include fdl.itexi
+@node LilyPond command index
+@appendix LilyPond command index
+
+@untranslated
+
+
+@node LilyPond index
+@appendix LilyPond index
+
+@untranslated
+
+
+@bye
+
+@c -- SKELETON FILE --
--- /dev/null
+depth = ../../..
+
+LOCALSTEPMAKE_TEMPLATES = ly
+
+include $(depth)/make/stepmake.make
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Changing defaults
+@chapter Changing defaults
+
+@untranslated
+
+
+@c index Internals Reference
+@c leave the @uref as one long line.
+@c ode{#}.@footnote{@rlearning{Scheme tutorial}, contains a short tutorial
+@menu
+* Interpretation contexts::
+* Explaining the Internals Reference::
+* Modifying properties::
+* Useful concepts and properties::
+* Advanced tweaks::
+@end menu
+
+@node Interpretation contexts
+@section Interpretation contexts
+
+@untranslated
+
+
+@menu
+* Contexts explained::
+* Creating contexts::
+* Keeping contexts alive::
+* Modifying context plug-ins::
+* Changing context default settings::
+* Defining new contexts::
+* Aligning contexts::
+@end menu
+
+@node Contexts explained
+@subsection Contexts explained
+
+@untranslated
+
+
+@c TODO Rethink and rewrite
+@c TODO Improve layout, order and consistency of wording -td
+@c TODO Add introduction which explains contexts in generality -td
+@c TODO Describe propagation of property values -td
+@menu
+* Score - the master of all contexts::
+* Top-level contexts - staff containers::
+* Intermediate-level contexts - staves::
+* Bottom-level contexts - voices::
+@end menu
+
+@node Score - the master of all contexts
+@unnumberedsubsubsec Score - the master of all contexts
+
+@untranslated
+
+
+@c ode{\score @{@dots{}@}} or @code{\layout @{@dots{}@}} block is
+@node Top-level contexts - staff containers
+@unnumberedsubsubsec Top-level contexts - staff containers
+
+@untranslated
+
+
+@node Intermediate-level contexts - staves
+@unnumberedsubsubsec Intermediate-level contexts - staves
+
+@untranslated
+
+
+@c ode{Voice} contexts.
+@node Bottom-level contexts - voices
+@unnumberedsubsubsec Bottom-level contexts - voices
+
+@untranslated
+
+
+@node Creating contexts
+@subsection Creating contexts
+
+@untranslated
+
+
+@c TODO \new Score and \score
+@c TODO more complete descriptions rather than learning style
+@c index new contexts
+@c index Context, creating
+@c ode{Voice}). This command creates a new context, and starts
+@c ode{\new Staff}.
+@c index creating contexts
+@ref{Running a function on all layout objects}). Without an explicit
+@c ode{\context}, it is usually applied to @code{Voice}
+@node Keeping contexts alive
+@subsection Keeping contexts alive
+
+@untranslated
+
+
+@c index contexts, keeping alive
+@c index contexts, lifetime
+@c ode{\change} commands, associating lyrics with a voice with
+@c ode{\lyricsto} commands, or when adding further musical events to
+@c ode{Voice} contexts in a @code{Staff} context or in a
+@c ode{<<...>>} construct will always persist to the end of the
+@c ode{<<...>>} constructs.
+@c index lyrics, aligning with sporadic melody
+@node Modifying context plug-ins
+@subsection Modifying context plug-ins
+
+@untranslated
+
+
+@c TODO Should this be Modifying engravers or Modifying contexts?
+@c ode{Note_head_engraver} and the @code{Staff} context contains a
+@c ode{Key_signature_engraver}.
+@c ode{Clef_engraver} from a @code{Staff} context,
+@c ode{Staff} context, we can have a score where each staff has its own
+@c index polymetric scores
+@c index Time signatures, multiple
+@c ode{Bar_engraver} must normally be first, and
+@node Changing context default settings
+@subsection Changing context default settings
+
+@untranslated
+
+
+@c ode{Score}, @code{Staff} and @code{Voice} contexts may be specified
+@c ode{Voice} contexts in a similar way.
+@c ode{\Staff} settings. If you wish to change the defaults for a
+@c TODO: add \with in here.
+@node Defining new contexts
+@subsection Defining new contexts
+
+@untranslated
+
+
+@c ode{Voice} context from scratch. It will be similar to
+@c ode{Voice}, but only prints centered slash note heads. It can be used
+@c ode{\layout} block,
+@node Aligning contexts
+@subsection Aligning contexts
+
+@untranslated
+
+
+@c TODO Better example needed. Ref LM, and expand on it.
+@c index ossia
+@c index nested contexts
+@c index contexts, nested
+@node Explaining the Internals Reference
+@section Explaining the Internals Reference
+
+@untranslated
+
+
+@menu
+* Navigating the program reference::
+* Layout interfaces::
+* Determining the grob property::
+* Naming conventions::
+@end menu
+
+@node Navigating the program reference
+@subsection Navigating the program reference
+
+@untranslated
+
+
+@c TODO remove this (it's in the LM)
+@c Replace with more factual directions
+@ref{Fingering instructions}), you will notice:
+@quotation
+@end quotation
+@c outdated info; probably will delete.
+@quotation
+@end quotation
+@quotation
+@end quotation
+@c ode{Fingering_engraver} plug-in will process them.
+@c I can't figure out what this is supposed to mean. -gp
+@c old info? it doesn't make any sense to me with our current docs.
+@quotation
+@end quotation
+@c ode{Music definitions}
+@node Layout interfaces
+@subsection Layout interfaces
+
+@untranslated
+
+
+@c index interface, layout
+@c index layout interface
+@c index grob
+@c ode{Fingering} object. For example, the page says
+@quotation
+@c ode{padding} (dimension, in staff space):
+@c ode{0.5}
+@end quotation
+@quotation
+@end quotation
+@node Determining the grob property
+@subsection Determining the grob property
+
+@untranslated
+
+
+@c TODO remove this (it's in the LM)
+@c Replace with more factual directions
+@quotation
+@c ode{side-position-interface}
+@end quotation
+@c index padding
+@quotation
+@end quotation
+@quotation
+@end quotation
+@node Naming conventions
+@subsection Naming conventions
+
+@untranslated
+
+
+@node Modifying properties
+@section Modifying properties
+
+@untranslated
+
+
+@c TODO change the menu and subsection node names to use
+@c backslash once the new macro to handle the refs
+@c is available. Need to find and change all refs at
+@c the same time. -td
+@menu
+* Overview of modifying properties::
+* The set command::
+* The override command::
+* The tweak command::
+* set versus override::
+@end menu
+
+@node Overview of modifying properties
+@subsection Overview of modifying properties
+
+@untranslated
+
+
+@c ode{Stem} or @code{NoteHead}, and @var{property} is an internal
+@c ode{\once} applies the change during one timestep only.
+@c ode{Beam} comes after the Beam is started, so it has no effect.
+@c ode{\revert} in the next example does not do anything.
+@c leave this as a long long
+@node The set command
+@subsection The @code{\set} command
+
+@untranslated
+
+
+@c index properties
+@c index changing properties
+@c ode{Lyrics}) is used. In this example,
+@c ode{Voice}s in the current stave. The change is applied
+@c index \once
+@node The override command
+@subsection The @code{\override} command
+
+@untranslated
+
+
+@c index internal documentation
+@c index finding graphical objects
+@c index graphical object descriptions
+@c index tweaking
+@c index internal documentation
+@node The tweak command
+@subsection The @code{\tweak} command
+
+@untranslated
+
+
+@c index tweaking
+@c index chord, modifying one note in
+@c ode{ChordEvent} event before the note, so separating the tweak
+@c ode{ChordEvent} in the music stream, so remaining adjacent to the
+@c TODO expand to include any further uses of \tweak
+@c TODO add examples of these
+@c ode{\tweak} command in the input stream by the automatic
+@ref{Displaying music expressions}.
+@c index tweaks in a variable
+@c index tweaks in lyrics
+@c index tweaking control points
+@c index control points, tweaking
+@node set versus override
+@subsection @code{\set} vs. @code{\override}
+
+@untranslated
+
+
+@c ode{\override}. There are actually two different kinds of
+@c ode{studlyCaps}. They mostly control the translation from
+@c ode{measurePosition} is an obvious example of
+@c ode{\override} is actually a shorthand;
+@c leave this long line -gp
+@c ode{dashed-words}. The values of grob properties change
+@c ode{fontSize} is a special property: it is equivalent to
+@node Useful concepts and properties
+@section Useful concepts and properties
+
+@untranslated
+
+
+@menu
+* Input modes::
+* Direction and placement::
+* Context layout order::
+* Distances and measurements::
+* Staff symbol properties::
+* Spanners::
+* Visibility of objects::
+* Line styles::
+* Rotating objects::
+@end menu
+
+@node Input modes
+@subsection Input modes
+
+@untranslated
+
+
+@ref{Chord notation}. Chords are rendered as notes on a staff.
+@ref{Basic percussion notation}.
+@ref{Entering figured bass}.
+@ref{Default tablatures}.
+@ref{Automatic fret diagrams} or you can enter them as a markup
+@ref{Fret diagram markups}).
+@c ode{\lyricsto} command which associates the following lyrics
+@ref{Text markup commands}.
+@c silly work-around for texinfo broken-ness
+@c (@strong{Note...} causes a spurious cross-reference in Info)
+@c ode{\notemode} command. Input is interpreted as pitches,
+@node Direction and placement
+@subsection Direction and placement
+
+@untranslated
+
+
+@c TODO Add table showing these
+@c ode{DOWN} may be used instead of @code{1} and @code{-1}
+@c ode{direction} to @code{0} or @code{CENTER}. Alternatively,
+@c ode{\xxxUp}, @code{xxxDown}, @code{xxxNeutral}
+@c ode{1} or @code{RIGHT} means @qq{to the right}. @code{0}
+@node Context layout order
+@subsection Context layout order
+
+@untranslated
+
+
+@c index contexts, layout order
+@node Distances and measurements
+@subsection Distances and measurements
+
+@untranslated
+
+
+@c index distances, absolute
+@c index distances, scaled
+@c ode{\in}@tie{}(inches), or @code{\pt}@tie{}(points, 1/72.27
+@c ode{\staff-space} to the quantity.
+@c ode{StaffSymbol}. Scaled distances automatically scale with any
+@c ode{staff-space} property of @code{StaffSymbol}, but fonts scale
+@c ode{staff-space} property of @code{StaffSymbol} and the size of
+@c ode{staff-space}. For an explanation and an example of its use,
+@ref{Page formatting},
+@ref{Setting the staff size}.
+@node Staff symbol properties
+@subsection Staff symbol properties
+
+@untranslated
+
+
+@c index adjusting staff symbol
+@c index drawing staff symbol
+@c index staff symbol, setting of
+@c TODO Extend or remove this section. See also NR 1.6.2 Staff symbol
+@c Need to think of uses for these properties. Eg 'line-positions
+@c is used in a snippet to thicken centre line.
+@c If retained, add @ref to here in 1.6.2 -td
+@c ode{'line-count} property. The number of staff lines is
+@node Spanners
+@subsection Spanners
+
+@untranslated
+
+
+@unnumberedsubsubsec Using the @code{spanner-interface}
+@c ode{minimum-length} property. Increasing this usually has the
+@c ode{springs-and-rods} property is set:
+@c ode{to-barline}. By default this is true, causing hairpins and
+@unnumberedsubsubsec Using the @code{line-spanner-interface}
+@c ode{ly:line-interface::print}. This routine determines the
+@c ode{right} sub-lists of the @code{bound-details} property
+@c ode{LEFT}) makes the line start/end at the left side of the note
+@c ode{Y} sub-properties. Setting either @code{stencil-align-dir-y}
+@c ode{DOWN} means align the @emph{bottom} edge of the text with
+@node Visibility of objects
+@subsection Visibility of objects
+
+@untranslated
+
+
+@c index objects, visibility of
+@c index grobs, visibility of
+@c index visibility of objects
+@c ode{break-visibility} property can be overridden. The first
+@menu
+* Removing the stencil::
+* Making objects transparent::
+* Painting objects white::
+* Using break-visibility::
+* Special considerations::
+@end menu
+
+@node Removing the stencil
+@unnumberedsubsubsec Removing the stencil
+
+@untranslated
+
+
+@c index stencil, removing
+@c ode{\revert}.
+@node Making objects transparent
+@unnumberedsubsubsec Making objects transparent
+
+@untranslated
+
+
+@c index transparent, making objects
+@node Painting objects white
+@unnumberedsubsubsec Painting objects white
+
+@untranslated
+
+
+@c index objects, coloring
+@c index coloring objects
+@c index layers
+@c index printing order
+@c index overwriting objects
+@c index objects, overwriting
+@c index grobs, overwriting
+@c ode{1}, although a few objects, including @code{StaffSymbol} and
+@c ode{BarLine}, are assigned a value of @code{0}. The order of
+@c ode{layer} value @code{0}), so overwriting them. To change this,
+@c ode{layer}, say @code{-1}, so that it is drawn earlier:
+@node Using break-visibility
+@unnumberedsubsubsec Using break-visibility
+
+@untranslated
+
+
+@c TODO Add making other objects breakable
+@c index break-visibility
+@c ode{break-visibility} property to control their visibility
+@c Leave this ref on a newline - formats incorrectly otherwise -td
+@c omit Ambitus as it appears not to be affected by break-visibility -td
+@c @item @code{Ambitus} @tab as specified @tab @code{begin-of-line-visible}
+@c omit the following item until it can be explained -td
+@c @item @code{BreakAlignGroup} @tab @code{Score} @tab calculated
+@c omit KeyCancellation until it can be explained -td
+@c @item @code{KeyCancellation} @tab ?? @tab @code{begin-of-line-invisible}
+@c omit LeftEdge until it can be explained -td
+@c @item @code{LeftEdge} @tab @code{Score} @tab @code{center-invisible}
+@c ode{break-visibility} must be present, not all of them are
+@node Special considerations
+@unnumberedsubsubsec Special considerations
+
+@untranslated
+
+
+@c index key signature, visibility following explicit change
+@c index explicitKeySignatureVisibility
+@c index clef, visibility following explicit change
+@c index explicitClefVisibility
+@c ode{explicitClefVisibility} properties. These are the equivalent
+@c ode{break-visibility}. Both are properties of the Staff context,
+@c ode{\set} command. Both are set by default to @code{all-visible}.
+@c ode{break-visibility} must still be overridden in the appropriate
+@c TODO Add visibility of cautionary accidentals before notes
+@c index automaticBars
+@c index bar lines, suppressing
+@c TODO Add example
+@c index octavated clefs, visibility of
+@c index visibility of octavated clefs
+@c index clefs, visibility of octavation
+@c ode{OctavateEight} layout object. Its visibility is controlled
+@node Line styles
+@subsection Line styles
+
+@untranslated
+
+
+@c ode{ly:line-interface::print}. This routine determines the
+@c FIXME Complete
+@c ode{left} instead of @code{right}.
+@ref{Spanners}.
+@node Rotating objects
+@subsection Rotating objects
+
+@untranslated
+
+
+@menu
+* Rotating layout objects::
+* Rotating markup::
+@end menu
+
+@node Rotating layout objects
+@unnumberedsubsubsec Rotating layout objects
+
+@untranslated
+
+
+@c index rotating objects
+@c index objects, rotating
+@c index hairpins, angled
+@c index angled hairpins
+@node Rotating markup
+@unnumberedsubsubsec Rotating markup
+
+@untranslated
+
+
+@c ode{outside-staff-priority} property for text is set to @code{#f}
+@node Advanced tweaks
+@section Advanced tweaks
+
+@untranslated
+
+
+@menu
+* Aligning objects::
+* Vertical grouping of grobs::
+* Modifying stencils::
+* Modifying shapes::
+@end menu
+
+@ref{Explaining the Internals Reference},
+@ref{Modifying properties},
+@ref{Interfaces for programmers}.
+@node Aligning objects
+@subsection Aligning objects
+
+@untranslated
+
+
+@c ode{X-offset} and @code{Y-offset} properties. The value of
+@c ode{X-offset} gives the displacement from the x coordinate of
+@c ode{Y-offset} gives the displacement from the center line of the
+@c ode{Y-offset} may be set directly or may be set to be calculated
+@c ode{self-alignment-interface}.}
+@c ode{X-offset} have no effect.
+@menu
+* Setting @code{X-offset} and @code{Y-offset} directly::
+* Using the @code{side-position-interface}::
+* Using the @code{self-alignment-interface}::
+* Using the @code{break-alignable-interface}::
+@end menu
+
+@node Setting @code{X-offset} and @code{Y-offset} directly
+@unnumberedsubsubsec Setting @code{X-offset} and @code{Y-offset} directly
+
+@untranslated
+
+
+@c TODO write more
+@node Using the @code{side-position-interface}
+@unnumberedsubsubsec Using the @code{side-position-interface}
+
+@untranslated
+
+
+@c TODO add an example of each to the table
+@c TODO Add examples
+@node Using the @code{self-alignment-interface}
+@unnumberedsubsubsec Using the @code{self-alignment-interface}
+
+@untranslated
+
+
+@c ode{self-alignment-interface} is controlled by the value of
+@c ode{X-offset} property is set to
+@c ode{ly:self-alignment-interface::x-aligned-on-self}.
+@c ode{self-alignment-X} may be given any
+@c ode{CENTER} and @code{RIGHT} may be used instead of the values
+@c ode{-1, 0, 1} respectively.
+@c ode{ly:self-alignment-interface::y-aligned-on-self}. However,
+@c ode{CENTER}, @code{UP} may be substituted for @code{-1, 0, 1}
+@unnumberedsubsubsec Using the @code{aligned-on-parent} procedures
+@c Cannot document as they do not seem to operate consistently on all objects -td
+@c TODO investigate further
+@c TODO Add example
+@unnumberedsubsubsec Using the @code{centered-on-parent} procedures
+@c Cannot document as they do not seem to operate consistently on all objects -td
+@c TODO investigate further
+@c TODO The align-interface, BassFigureAlignment and VerticalAlignment
+@node Using the @code{break-alignable-interface}
+@unnumberedsubsubsec Using the @code{break-alignable-interface}
+
+@untranslated
+
+
+@c index align to objects
+@c index break-align-symbols
+@c ode{breathing-sign}, @code{clef}, @code{custos}, @code{staff-bar},
+@c ode{left-edge}, @code{key-cancellation}, @code{key-signature}, and
+@c ode{time-signature}.
+@node Vertical grouping of grobs
+@subsection Vertical grouping of grobs
+
+@untranslated
+
+
+@c FIXME Expand this section
+@node Modifying stencils
+@subsection Modifying stencils
+
+@untranslated
+
+
+@c ode{MultiMeasureRest} object is @code{ly:multi-measure-rest::print}.
+@c ode{stencil} property to reference a different, specially-written,
+@c ode{text} property to the object which is set to contain the
+@ref{Graphic notation inside markup}.
+@c ode{\musicglyph} markup command -- see @ref{The Feta font}.
+@c TODO Add inserting eps files or ref to later
+@c TODO Add inserting Postscript or ref to later
+@ref{Graphic notation inside markup},
+@ref{Formatting text},
+@ref{Text markup commands},
+@ref{The Feta font}.
+@node Modifying shapes
+@subsection Modifying shapes
+
+@untranslated
+
+
+@menu
+* Modifying ties and slurs::
+@end menu
+
+@node Modifying ties and slurs
+@unnumberedsubsubsec Modifying ties and slurs
+
+@untranslated
+
+
+@c index slurs, modifying
+@c index ties, modifying
+@c index Bézier curves
+@c index Bézier control points
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@c TODO: add tablature.
+@node Cheat sheet
+@appendix Cheat sheet
+
+@untranslated
+
+
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c Don't replace quotes with directed quotes.
+@set txicodequoteundirected
+@set txicodequotebacktick
+@c ***** Displaying text *****
+@c We need this since @q{\} doesn't work with makeinfo 4.11 --
+@c say @q{@bs{}} instead.
+@c ***** Displaying images not generated by lilypond-book *****
+@c Current installation setup of Info docs requires that all images are
+@c expected to be found in the `lilypond/' subdirectory. `lilypond-book'
+@c already generates proper @image commands for images of music; these
+@c macro definitions do the same for other images.
+@c ***** Headers *****
+@c ***** Indexing *****
+@c Don't remove the `@c' within the macro definition! See section 19.3,
+@c `Macro Details and Caveats', in the texinfo info file for explanation.
+@c
+@c ***** Macros specific to translated docs *****
+@c ugh, cannot set/define global variable 'translationof' in any way :-(
+@set translationof \TEXT\
+@c ***** Macros specific to the web site *****
+@c keep the space for proper nesting of </p>
+@c not strictly necessary, but it makes things easier for updating news
+@c keep the space for proper nesting of </p>
+@c @image{\IMAGE-FILE\}
+@c @image{\IMAGE-FILE\}
+@c @image{\IMAGE-FILE\}
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@quotation
+@end quotation
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@node GNU Free Documentation License
+@appendix GNU Free Documentation License
+
+@untranslated
+
+
+@c index FDL, GNU Free Documentation License
+@c enter Version 1.1, March 2000
+@subheading ADDENDUM: How to use this License for your documents
+@c Local Variables:
+@c ispell-local-pdict: "ispell-dict"
+@c End:
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node General input and output
+@chapter General input and output
+
+@untranslated
+
+
+@menu
+* Input structure::
+* Titles and headers::
+* Working with input files::
+* Controlling output::
+* MIDI output::
+@end menu
+
+@node Input structure
+@section Input structure
+
+@untranslated
+
+
+@menu
+* Structure of a score::
+* Multiple scores in a book::
+* File structure::
+@end menu
+
+@node Structure of a score
+@subsection Structure of a score
+
+@untranslated
+
+
+@ref{File structure}.) Both single-line comments and comments
+@c ode{\score} block.
+@node Multiple scores in a book
+@subsection Multiple scores in a book
+
+@untranslated
+
+
+@c index movements, multiple
+@c ode{\book} block will result in a separate output. If you do not
+@c ode{\book}, but if it is not present, the @code{\header} which is at
+@node File structure
+@subsection File structure
+
+@untranslated
+
+
+@c ode{\layout}. Such a definition at the toplevel changes the default
+@c ode{#(set-default-paper-size "a7" 'landscape)} or
+@c ode{#(ly:set-option 'point-and-click #f)}.
+@c ode{toplevel-score-handler} at toplevel. The default handler is
+@c ode{\book} blocks in a @code{.ly} file is if you wish to create
+@c ode{toplevel-music-handler} at toplevel. The default handler is
+@c index variables
+@c index whitespace
+@c ode{\override} and @code{\set} commands. In particular, spaces
+@c ode{\override Score . LyricText #'font-size = #5} and before and
+@node Titles and headers
+@section Titles and headers
+
+@untranslated
+
+
+@menu
+* Creating titles::
+* Custom titles::
+* Reference to page numbers::
+* Table of contents::
+@end menu
+
+@node Creating titles
+@subsection Creating titles
+
+@untranslated
+
+
+@c ode{\bookpart} blocks).
+@c index page breaks, forcing
+@c ode{\header} inside @code{\score}) by using
+@c index copyright
+@c index tagline
+@c ode{copyright} field from @code{\header} is inserted, and the last
+@node Custom titles
+@subsection Custom titles
+
+@untranslated
+
+
+@c index \paper
+@c index header
+@c index footer
+@c index page layout
+@c index titles
+@node Reference to page numbers
+@subsection Reference to page numbers
+
+@untranslated
+
+
+@c ode{\label},
+@c ode{\page-ref}.
+@node Table of contents
+@subsection Table of contents
+
+@untranslated
+
+
+@c ode{\table-of-contents},
+@c ode{\tocItem}.
+@node Working with input files
+@section Working with input files
+
+@untranslated
+
+
+@menu
+* Including LilyPond files::
+* Different editions from one source::
+* Text encoding::
+* Displaying LilyPond notation::
+@end menu
+
+@node Including LilyPond files
+@subsection Including LilyPond files
+
+@untranslated
+
+
+@c index including files
+@c ode{\include} statements are not interpreted until they have
+@c ode{-drelative-includes} option at the command line
+@node Different editions from one source
+@subsection Different editions from one source
+
+@untranslated
+
+
+@menu
+* Using variables::
+* Using tags::
+@end menu
+
+@node Using variables
+@unnumberedsubsubsec Using variables
+
+@untranslated
+
+
+@c index variables, use of
+@node Using tags
+@unnumberedsubsubsec Using tags
+
+@untranslated
+
+
+@c index tag
+@c index keep tagged music
+@c index remove tagged music
+@c ode{\removeWithTag #'@var{name}}. The result of applying these filters
+@c ode{\removeWithTag}
+@c ode{\removeWithTag} commands should be a symbol
+@c ode{\tag} entries:
+@ref{Automatic part combining},
+@ref{Including LilyPond files}.
+@c This warning is more general than this placement implies.
+@c Rests are not merged whether or not they come from tagged sections.
+@c Should be deleted? -td
+@node Text encoding
+@subsection Text encoding
+
+@untranslated
+
+
+@c index Unicode
+@c index UTF-8
+@c index non-ASCII characters
+@c ode{\markup} block, where @code{hhhh} is the hexadecimal code for
+@c index copyright sign
+@node Displaying LilyPond notation
+@subsection Displaying LilyPond notation
+
+@untranslated
+
+
+@c TODO What happens under Windows?
+@node Controlling output
+@section Controlling output
+
+@untranslated
+
+
+@menu
+* Extracting fragments of music::
+* Skipping corrected music::
+* Alternative output formats::
+@end menu
+
+@node Extracting fragments of music
+@subsection Extracting fragments of music
+
+@untranslated
+
+
+@c ode{-dclip-systems}. The clips are output as EPS files, and are
+@node Skipping corrected music
+@subsection Skipping corrected music
+
+@untranslated
+
+
+@node Alternative output formats
+@subsection Alternative output formats
+
+@untranslated
+
+
+@c index scalable vector graphics output
+@c index SVG output
+@c index encapsulated postscript output
+@c index EPS output
+@node MIDI output
+@section MIDI output
+
+@untranslated
+
+
+@c index Sound
+@c index MIDI
+@c TODO Check this
+@menu
+* Creating MIDI files::
+* MIDI block::
+* What goes into the MIDI output?::
+* Repeats in MIDI::
+* Controlling MIDI dynamics::
+* Percussion in MIDI::
+@end menu
+
+@node Creating MIDI files
+@subsection Creating MIDI files
+
+@untranslated
+
+
+@c ode{\midi} block to a score, for example,
+@c ode{\layout} block, only MIDI output will be produced. When
+@c ode{.midi}.
+@unnumberedsubsubsec Instrument names
+@c index instrument names
+@c ode{Staff.midiInstrument} property to the instrument name.
+@c In 2.11 the following no longer seems to be a problem -td
+@node MIDI block
+@subsection MIDI block
+
+@untranslated
+
+
+@c index MIDI block
+@c index MIDI context definitions
+@c ode{\midi@{ @}} block.
+@node What goes into the MIDI output?
+@subsection What goes into the MIDI output?
+
+@untranslated
+
+
+@c TODO Check grace notes - timing is suspect?
+@unnumberedsubsubsec Supported in MIDI
+@c index Pitches in MIDI
+@c index MIDI, Pitches
+@c index Quarter tones in MIDI
+@c index MIDI, quarter tones
+@c index Microtones in MIDI
+@c index MIDI, microtones
+@c index Chord names in MIDI
+@c index MIDI, chord names
+@c index Rhythms in MIDI
+@c index MIDI, Rhythms
+@c TODO etc
+@unnumberedsubsubsec Unsupported in MIDI
+@c TODO index as above
+@node Repeats in MIDI
+@subsection Repeats in MIDI
+
+@untranslated
+
+
+@c index repeats in MIDI
+@c ode{\unfoldRepeats} music function. This function changes all
+@node Controlling MIDI dynamics
+@subsection Controlling MIDI dynamics
+
+@untranslated
+
+
+@unnumberedsubsubsec Dynamic marks
+@c ode{Score.dynamicAbsoluteVolumeFunction} to this function.
+@c ode{\rfz}, is required, this will not by default
+@unnumberedsubsubsec Overall MIDI volume
+@c ode{midiMaximumVolume} at the @code{Score} level. These
+@unnumberedsubsubsec Equalizing different instruments (i)
+@unnumberedsubsubsec Equalizing different instruments (ii)
+@c ode{instrumentEqualizer} in the @code{Score} context to a new
+@c ode{dynamicAbsoluteVolumeFunction} at the start of this section.
+@c Delete when satisfied this is adequately covered elsewhere -td
+@c index microtones in MIDI
+@node Percussion in MIDI
+@subsection Percussion in MIDI
+
+@untranslated
+
+
+@c ode{DrumStaff} context, to obtain the correct MIDI output.
+@c TODO Expand with examples, and any other issues
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: us-ascii; mode: texinfo; -*-
+@include version.itexi
+@include common-macros.itexi
+@c ***** Displaying text *****
+@c To get decent quotes in `foo' and ``foo''.
+@c artouche
+@quotation
+@quotation
+@c artouche
+@end quotation
+@end quotation
+@c ***** Headings in a doc subsection *****
+@c Don't insert an empty line after @predefined! Right now
+@c it doesn't matter, but a future implementation will probably
+@c add some code which needs this restriction.
+@subsubheading Predefined commands
+@c The next macro is a dummy currently since texinfo doesn't
+@c provide a real ragged-right environment yet.
+@c
+@c Due to a bug in texi2html (texi2html.pl CVS versions <= 1.245)
+@c the macro must not be empty.
+@c
+@subsubheading Selected Snippets
+@c Don't insert an empty line after @seealso! Otherwise we get
+@c unwanted extra vertical space in the PDF output.
+@subsubheading See also
+@subsubheading Known issues and warnings
+@c ***** Links and references *****
+@c Definitions for references:
+@c
+@c @rglos
+@c @rlearning
+@c @ruser
+@c @ressay
+@c @rprogram
+@c @rlsr
+@c @rinternals
+@c
+@c All these also have a @...named version which allows to specify the
+@c displayed text for the reference as second argument.
+@c
+@c ***** HTML + bigpage is a special case (other manual names); all other
+@c formats are treated similarly.
+@c *** not TeX ***
+@ifnottex
+@c ** bigpage **
+@ref{\TEXT\,,,music-glossary-big-page,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary-big-page,Music Glossary}
+@ref{\TEXT\,,,learning-big-page,Learning Manual}
+@ref{\TEXT\,,\DISPLAY\,learning-big-page,Learning Manual}
+@ref{\TEXT\,,,notation-big-page,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation-big-page,Notation Reference}
+@ref{\TEXT\,,,essay-big-page,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay-big-page,Essay}
+@ref{\TEXT\,,,application-big-page,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application-big-page,Application Usage}
+@ref{\TEXT\,,,snippets-big-page,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets-big-page,Snippets}
+@ref{\TEXT\,,,internals-big-page,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals-big-page,Internals Reference}
+@c ** not bigpage **
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,,notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation,Notation Reference}
+@ref{\TEXT\,,,essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@ref{\TEXT\,,,application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application,Application Usage}
+@ref{\TEXT\,,,snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets,Snippets}
+@ref{\TEXT\,,,internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals,Internals Reference}
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@ref{\TEXT\,,,lilypond-learning,Learning Manual}
+@ref{\TEXT\,,,lilypond-notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,lilypond-notation,Notation Reference}
+@ref{\TEXT\,,,lilypond-essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,lilypond-essay,Essay}
+@ref{\TEXT\,,,lilypond-application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,lilypond-application,Application Usage}
+@ref{\TEXT\,,,lilypond-snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,lilypond-snippets,Snippets}
+@ref{\TEXT\,,,lilypond-internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,lilypond-internals,Internals Reference}
+@end ifnottex
+@c *** TeX ***
+@c All commands below should work in the middle of the line;
+@c we thus must not use @vindex directly since it works only if placed
+@c on a line of its own. To overcome this problem, we define a
+@c replacement macro using the internal definition of @vindex which
+@c delimits arguments in the standard way (i.e., with braces).
+@ref{\TEXT\,,,music-glossary,Music Glossary}
+@ref{\TEXT\,,\DISPLAY\,music-glossary,Music Glossary}
+@ref{\TEXT\,,,learning,Learning Manual}
+@ref{\TEXT\,,\DISPLAY\,learning,Learning Manual}
+@ref{\TEXT\,,,notation,Notation Reference}
+@ref{\TEXT\,,\DISPLAY\,notation,Notation Reference}
+@ref{\TEXT\,,,essay,Essay}
+@ref{\TEXT\,,\DISPLAY\,essay,Essay}
+@ref{\TEXT\,,,application,Application Usage}
+@ref{\TEXT\,,\DISPLAY\,application,Application Usage}
+@ref{\TEXT\,,,snippets,Snippets}
+@ref{\TEXT\,,\DISPLAY\,snippets,Snippets}
+@ref{\TEXT\,,,internals,Internals Reference}
+@ref{\TEXT\,,\DISPLAY\,internals,Internals Reference}
+@c ***** Macros specific to the web site *****
+@c LEGALESE
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Notation manual tables
+@appendix Notation manual tables
+
+@untranslated
+
+
+@c Please do not delete the following @ignore block.
+* Text markup commands::
+* Text markup list commands::
+* Note head styles::
+* List of articulations::
+@menu
+* Chord name chart::
+* Common chord modifiers::
+* Predefined fretboard diagrams::
+* MIDI instruments::
+* List of colors::
+* The Feta font::
+* Note head styles::
+* Text markup commands::
+* Text markup list commands::
+* List of articulations::
+* Percussion notes::
+* Technical glossary::
+* All context properties::
+* Layout properties::
+* Identifiers::
+* Scheme functions::
+@end menu
+
+@node Chord name chart
+@appendixsec Chord name chart
+
+@untranslated
+
+
+@node Common chord modifiers
+@appendixsec Common chord modifiers
+
+@untranslated
+
+
+@c ode{\chordmode} to generate standard chord structures.
+@c ode{5} or nothing
+@c ode{m} or @code{m5}
+@c ode{aug}
+@c ode{dim}
+@c ode{7}
+@c ode{maj7} or @code{maj}
+@c ode{m7}
+@c ode{dim7}
+@c ode{aug7}
+@c ode{m7.5-}
+@c ode{maj7.5-}
+@c ode{6}
+@c ode{m6}
+@c ode{9}
+@c ode{maj9}
+@c ode{m9}
+@c ode{11}
+@c ode{maj11}
+@c ode{m11}
+@c ode{13}
+@c ode{13.11}
+@c ode{maj13.11}
+@c ode{m13.11}
+@c ode{sus2}
+@c ode{sus4}
+@node Predefined fretboard diagrams
+@appendixsec Predefined fretboard diagrams
+
+@untranslated
+
+
+@node MIDI instruments
+@appendixsec MIDI instruments
+
+@untranslated
+
+
+@c ode{midiInstrument} property.
+@node List of colors
+@appendixsec List of colors
+
+@untranslated
+
+
+@subsubheading Normal colors
+@c index List of colors
+@c index Colors, list of
+@subsubheading X color names
+@subsubheading Color Names without a numerical suffix:
+@subsubheading Color names with a numerical suffix
+@subsubheading Grey Scale
+@node The Feta font
+@appendixsec The Feta font
+
+@untranslated
+
+
+@c index Feta font
+@c index Font, Feta
+@menu
+* Clef glyphs::
+* Time Signature glyphs::
+* Number glyphs::
+* Accidental glyphs::
+* Default Notehead glyphs::
+* Special Notehead glyphs::
+* Shape-note Notehead glyphs::
+* Rest glyphs::
+* Flag glyphs::
+* Dot glyphs::
+* Dynamic glyphs::
+* Script glyphs::
+* Arrowhead glyphs::
+* Bracket-tip glyphs::
+* Pedal glyphs::
+* Accordion glyphs::
+* Vaticana glyphs::
+* Medicaea glyphs::
+* Hufnagel glyphs::
+* Mensural glyphs::
+* Neomensural glyphs::
+* Petrucci glyphs::
+* Solesmes glyphs::
+@end menu
+
+@node Clef glyphs
+@unnumberedsubsec Clef glyphs
+
+@untranslated
+
+
+@node Time Signature glyphs
+@unnumberedsubsec Time Signature glyphs
+
+@untranslated
+
+
+@node Number glyphs
+@unnumberedsubsec Number glyphs
+
+@untranslated
+
+
+@node Accidental glyphs
+@unnumberedsubsec Accidental glyphs
+
+@untranslated
+
+
+@node Default Notehead glyphs
+@unnumberedsubsec Default Notehead glyphs
+
+@untranslated
+
+
+@node Special Notehead glyphs
+@unnumberedsubsec Special Notehead glyphs
+
+@untranslated
+
+
+@node Shape-note Notehead glyphs
+@unnumberedsubsec Shape-note Notehead glyphs
+
+@untranslated
+
+
+@node Rest glyphs
+@unnumberedsubsec Rest glyphs
+
+@untranslated
+
+
+@node Flag glyphs
+@unnumberedsubsec Flag glyphs
+
+@untranslated
+
+
+@node Dot glyphs
+@unnumberedsubsec Dot glyphs
+
+@untranslated
+
+
+@node Dynamic glyphs
+@unnumberedsubsec Dynamic glyphs
+
+@untranslated
+
+
+@node Script glyphs
+@unnumberedsubsec Script glyphs
+
+@untranslated
+
+
+@node Arrowhead glyphs
+@unnumberedsubsec Arrowhead glyphs
+
+@untranslated
+
+
+@node Bracket-tip glyphs
+@unnumberedsubsec Bracket-tip glyphs
+
+@untranslated
+
+
+@node Pedal glyphs
+@unnumberedsubsec Pedal glyphs
+
+@untranslated
+
+
+@node Accordion glyphs
+@unnumberedsubsec Accordion glyphs
+
+@untranslated
+
+
+@node Vaticana glyphs
+@unnumberedsubsec Vaticana glyphs
+
+@untranslated
+
+
+@node Medicaea glyphs
+@unnumberedsubsec Medicaea glyphs
+
+@untranslated
+
+
+@node Hufnagel glyphs
+@unnumberedsubsec Hufnagel glyphs
+
+@untranslated
+
+
+@node Mensural glyphs
+@unnumberedsubsec Mensural glyphs
+
+@untranslated
+
+
+@node Neomensural glyphs
+@unnumberedsubsec Neomensural glyphs
+
+@untranslated
+
+
+@node Petrucci glyphs
+@unnumberedsubsec Petrucci glyphs
+
+@untranslated
+
+
+@node Solesmes glyphs
+@unnumberedsubsec Solesmes glyphs
+
+@untranslated
+
+
+@node Note head styles
+@appendixsec Note head styles
+
+@untranslated
+
+
+@c index note head styles
+@include markup-commands.tely
+@include markup-list-commands.tely
+@node List of articulations
+@appendixsec List of articulations
+
+@untranslated
+
+
+@c index accent
+@c index marcato
+@c index staccatissimo
+@c index espressivo
+@c index fermata
+@c index stopped
+@c index staccato
+@c index portato
+@c index tenuto
+@c index upbow
+@c index downbow
+@c index foot marks
+@c index organ pedal marks
+@c index turn
+@c index open
+@c index stopped
+@c index flageolet
+@c index reverseturn
+@c index trill
+@c index prall
+@c index mordent
+@c index prallprall
+@c index prallmordent
+@c index prall, up
+@c index prall, down
+@c index thumb marking
+@c index segno
+@c index coda
+@c index varcoda
+@node Percussion notes
+@appendixsec Percussion notes
+
+@untranslated
+
+
+@node Technical glossary
+@appendixsec Technical glossary
+
+@untranslated
+
+
+@menu
+* callback::
+* glyph::
+* grob::
+* interface::
+* lexer::
+* output-def::
+* parser::
+* parser variable::
+* prob::
+* simple-closure::
+* smob::
+* stencil::
+@end menu
+
+@node callback
+@unnumberedsubsec callback
+
+@untranslated
+
+
+@c index callback
+@node glyph
+@unnumberedsubsec glyph
+
+@untranslated
+
+
+@c index glyph
+@c index font
+@c index typeface
+@ref{Fonts},
+@ref{Text encoding}.
+@node grob
+@unnumberedsubsec grob
+
+@untranslated
+
+
+@c index grob
+@c index layout objects
+@c index graphical objects
+@node interface
+@unnumberedsubsec interface
+
+@untranslated
+
+
+@c index interface
+@c index grob-interface
+@c index graphical object interfaces
+@ref{Layout interfaces}.
+@node lexer
+@unnumberedsubsec lexer
+
+@untranslated
+
+
+@c index lexer
+@node output-def
+@unnumberedsubsec output-def
+
+@untranslated
+
+
+@c index output-def
+@node parser
+@unnumberedsubsec parser
+
+@untranslated
+
+
+@c index parser
+@node parser variable
+@unnumberedsubsec parser variable
+
+@untranslated
+
+
+@c ode{\score} blocks as well as external files added with the
+@c ode{\include} command. This can lead to unintended consequences
+@node prob
+@unnumberedsubsec prob
+
+@untranslated
+
+
+@node simple-closure
+@unnumberedsubsec simple-closure
+
+@untranslated
+
+
+@node smob
+@unnumberedsubsec smob
+
+@untranslated
+
+
+@node stencil
+@unnumberedsubsec stencil
+
+@untranslated
+
+
+@node All context properties
+@appendixsec All context properties
+
+@untranslated
+
+
+@include context-properties.tely
+@node Layout properties
+@appendixsec Layout properties
+
+@untranslated
+
+
+@include layout-properties.tely
+@node Identifiers
+@appendixsec Identifiers
+
+@untranslated
+
+
+@include identifiers.tely
+@node Scheme functions
+@appendixsec Scheme functions
+
+@untranslated
+
+
+@include scheme-functions.tely
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Musical notation
+@chapter Musical notation
+
+@untranslated
+
+
+@menu
+* Pitches::
+* Rhythms::
+* Expressive marks::
+* Repeats::
+* Simultaneous notes::
+* Staff notation::
+* Editorial annotations::
+* Text::
+@end menu
+
+@include notation/pitches.itely
+@include notation/rhythms.itely
+@include notation/expressive.itely
+@include notation/repeats.itely
+@include notation/simultaneous.itely
+@include notation/staff.itely
+@include notation/editorial.itely
+@include notation/text.itely
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Interfaces for programmers
+@chapter Interfaces for programmers
+
+@untranslated
+
+
+@menu
+* Music functions::
+* Programmer interfaces::
+* Building complicated functions::
+* Markup programmer interface::
+* Contexts for programmers::
+* Scheme procedures as properties::
+* Using Scheme code instead of \tweak::
+* Difficult tweaks::
+@end menu
+
+@node Music functions
+@section Music functions
+
+@untranslated
+
+
+@menu
+* Overview of music functions::
+* Simple substitution functions::
+* Paired substitution functions::
+* Mathematics in functions::
+* Void functions::
+* Functions without arguments::
+* Overview of available music functions::
+@end menu
+
+@node Overview of music functions
+@subsection Overview of music functions
+
+@untranslated
+
+
+@node Simple substitution functions
+@subsection Simple substitution functions
+
+@untranslated
+
+
+@node Paired substitution functions
+@subsection Paired substitution functions
+
+@untranslated
+
+
+@quotation
+@end quotation
+@node Mathematics in functions
+@subsection Mathematics in functions
+
+@untranslated
+
+
+@node Void functions
+@subsection Void functions
+
+@untranslated
+
+
+@c ode{'void} property set to @code{#t}, the parser is told to
+@node Functions without arguments
+@subsection Functions without arguments
+
+@untranslated
+
+
+@node Overview of available music functions
+@subsection Overview of available music functions
+
+@untranslated
+
+
+@c fixme ; this should be move somewhere else?
+@include identifiers.tely
+@node Programmer interfaces
+@section Programmer interfaces
+
+@untranslated
+
+
+@menu
+* Input variables and Scheme::
+* Internal music representation::
+@end menu
+
+@node Input variables and Scheme
+@subsection Input variables and Scheme
+
+@untranslated
+
+
+@c ode{traLaLa}.
+@c ode{\layout} block also contains a @code{traLaLa} variable, which is
+@c
+@c ode{\midi}, and @code{\layout} blocks are scopes nested inside that
+@c ode{twice}:
+@c Due to parser lookahead
+@ref{Void functions}, or
+@c ode{--safe} option.
+@node Internal music representation
+@subsection Internal music representation
+
+@untranslated
+
+
+@c ode{note-event}, a @code{rhythmic-event}, and a
+@c ode{melodic-event}. All classes of music are listed in the
+@c ode{duration} properties that store the pitch and duration of that
+@c ode{element}. The body of a repeat is stored in the @code{element}
+@c ode{elements}.
+@node Building complicated functions
+@section Building complicated functions
+
+@untranslated
+
+
+@menu
+* Displaying music expressions::
+* Music properties::
+* Doubling a note with slurs (example)::
+* Adding articulation to notes (example)::
+@end menu
+
+@node Displaying music expressions
+@subsection Displaying music expressions
+
+@untranslated
+
+
+@c index internal storage
+@c index displaying music expressions
+@c index internal representation, displaying
+@c index displayMusic
+@c ode{AbsoluteDynamicEvent} with a @code{"f"} text property.
+@node Music properties
+@subsection Music properties
+
+@untranslated
+
+
+@c ode{'elements} property of @code{someNote}.
+@c ode{\displayMusic} to display the Scheme representation of a music
+@node Doubling a note with slurs (example)
+@subsection Doubling a note with slurs (example)
+
+@untranslated
+
+
+@c ode{'elements} property of each one, and finally make a
+@c ode{SequentialMusic} with the two @code{EventChords}.
+@node Adding articulation to notes (example)
+@subsection Adding articulation to notes (example)
+
+@untranslated
+
+
+@ref{Creating contexts}. However, suppose that we want to write
+@c ode{event-chord}. In Scheme, the type of variable is often clear
+@c ode{let} is used to declare local variables. Here we use one local
+@c ode{(ly:music-deep-copy event-chord)}. @code{ly:music-deep-copy} is
+@c ode{ly:}. It is use to make a copy of a music
+@c ode{EventChord} expression. It is better to not modify the
+@c ode{EventChord} which was given as an argument, because it may be
+@c ode{NoteEventChord} expression and is a copy of @code{event-chord}. We
+@c ode{result-event-chord} expression.
+@c ode{ly:music-property} is the function used to access music properties
+@c ode{ArticulationEvent} expression, which we copy from the
+@c ode{\displayMusic} output,
+@c ode{cons} is used to add an element to a list without modifying the
+@node Markup programmer interface
+@section Markup programmer interface
+
+@untranslated
+
+
+@menu
+* Markup construction in Scheme::
+* How markups work internally::
+* New markup command definition::
+* New markup list command definition::
+@end menu
+
+@node Markup construction in Scheme
+@subsection Markup construction in Scheme
+
+@untranslated
+
+
+@c index defining markup commands
+@quotation
+@end quotation
+@c ode{markup} macro. For example, You may use function calls inside
+@c ode{markup} in order to manipulate character strings. This is
+@ref{New markup command definition}).
+@c ode{#:center}, and @code{#:column} cannot be a variable or
+@c ode{make-center-markup}, or @code{make-column-markup} functions
+@node How markups work internally
+@subsection How markups work internally
+
+@untranslated
+
+
+@c ode{\raise} is actually represented by the @code{raise-markup}
+@c ode{raise-markup} function is called as
+@c ode{text example} string, and then it raises that Stencil by 0.5
+@node New markup command definition
+@subsection New markup command definition
+
+@untranslated
+
+
+@c ode{#'caps} for interpreting @code{Text-in-caps}.
+@c ode{padding} property) from the staff and the notes. To make sure
+@c ode{#:translate}, we add an empty string (@code{#:hspace 0}) before the
+@c ode{name} is moved in relation to that empty string. The net effect is
+@c ode{(make-line-markup ...)}. Finally, the resulting markup is passed
+@c ode{props} arguments.
+@ref{Text markup commands}, for details.
+@c ode{define-markup-command} are limited as follows.
+@c index Scheme signature
+@c index signature, Scheme
+@c ommand{lilypond} complains that it cannot parse @code{foo} due to its
+@node New markup list command definition
+@subsection New markup list command definition
+
+@untranslated
+
+
+@c ode{define-markup-list-command} Scheme macro, which is similar to the
+@c ode{define-markup-command} macro described in
+@ref{New markup command definition}, except that where the latter returns
+@c ode{paragraph} markup list command takes a markup list argument, named
+@c ode{args}. The predicate for markup lists is @code{markup-list?}.
+@c ode{par-indent}, from the property list @code{props} If the property
+@node Contexts for programmers
+@section Contexts for programmers
+
+@untranslated
+
+
+@menu
+* Context evaluation::
+* Running a function on all layout objects::
+@end menu
+
+@node Context evaluation
+@subsection Context evaluation
+
+@untranslated
+
+
+@c index calling code during interpreting
+@node Running a function on all layout objects
+@subsection Running a function on all layout objects
+
+@untranslated
+
+
+@c index calling code on layout objects
+@node Scheme procedures as properties
+@section Scheme procedures as properties
+
+@untranslated
+
+
+@c ode{AccidentalSuggestion},
+@c ode{ly:self-alignment-interface::centered-on-x-parent} are called
+@node Using Scheme code instead of \tweak
+@section Using Scheme code instead of @code{\tweak}
+
+@untranslated
+
+
+@c ode{^} and @code{_}.
+@c ode{m} (created with @code{make-music}) are extracted with
+@c ode{ly:music-property}, a new key-value pair to change the
+@c ode{acons} Scheme function, and the result is finally
+@c ode{let} block is the return value, @code{m} itself.
+@node Difficult tweaks
+@section Difficult tweaks
+
+@untranslated
+
+
+@c ode{after-line-breaking} callback contains the Scheme procedure that
+@c ode{my-callback}. This procedure
+@c ode{ly:hairpin::after-line-breaking} should also be called.
+@c ode{\overrideProperty} function, which works similar to @code{\once
+@c ode{NonMusicalPaperColumn} and @code{PaperColumn}, still works as
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Spacing issues
+@chapter Spacing issues
+
+@untranslated
+
+
+@c ode{\score @{...@}} blocks and contains settings that
+@menu
+* Paper and pages::
+* Music layout::
+* Breaks::
+* Vertical spacing::
+* Horizontal spacing::
+* Fitting music onto fewer pages::
+@end menu
+
+@node Paper and pages
+@section Paper and pages
+
+@untranslated
+
+
+@menu
+* Paper size::
+* Page formatting::
+@end menu
+
+@node Paper size
+@subsection Paper size
+
+@untranslated
+
+
+@c index paper size
+@c index page size
+@c ode{set-default-paper-size} and @code{set-paper-size}.
+@c ode{set-default-paper-size} must be placed in the toplevel
+@c ode{set-default-paper-size} sets the size of all pages, whereas
+@c ode{set-paper-size} only sets the size of the pages that the
+@c ode{\paper} block applies to. For example, if the @code{\paper}
+@c ode{\book}, then the paper size will only apply to that book.
+@c ode{letter}, @code{legal}, and @code{11x17} (also known as
+@c TODO add a new appendix for paper sizes (auto-generated) -pm
+@c ode{paper-alist} in the initialization file
+@c index orientation
+@c index landscape
+@c ode{set-default-paper-size}, pages will be rotated by 90
+@node Page formatting
+@subsection Page formatting
+
+@untranslated
+
+
+@menu
+* Vertical dimensions::
+* Horizontal dimensions::
+* Other layout variables::
+@end menu
+
+@node Vertical dimensions
+@unnumberedsubsubsec Vertical dimensions
+
+@untranslated
+
+
+@c ode{6\mm}.
+@c ode{evenHeaderMarkup}) and the title markup
+@c ode{5\mm}.
+@c ode{in}, @code{pt}, and @code{cm} are variables defined in
+@c ode{\paper} block, @code{page-music-height} and
+@c ode{page-make-stencil}. The former tells the line-breaking algorithm
+@ref{Vertical spacing between systems}.
+@node Horizontal dimensions
+@unnumberedsubsubsec Horizontal dimensions
+
+@untranslated
+
+
+@c ode{left-margin}, @code{indent}, and @code{short-indent} may
+@c ode{set-default-paper-size} or @code{set-paper-size}.
+@c ode{set-default-paper-size} or @code{set-paper-size}.
+@c ode{20\mm}, as determined by @code{set-default-paper-size} or
+@c ode{set-paper-size}.
+@c ode{set-default-paper-size} or @code{set-paper-size}.
+@c ode{line-width}.
+@node Other layout variables
+@unnumberedsubsubsec Other layout variables
+
+@untranslated
+
+
+@c ode{5}.
+@c ode{#1}.
+@c ode{between-system-padding} is set to something different than
+@ref{Vertical spacing between systems}.
+@c ode{1.4}. For details, see
+@ref{Vertical spacing between systems}.
+@c ode{##t}.
+@c ode{##f}.
+@node Music layout
+@section Music layout
+
+@untranslated
+
+
+@menu
+* Setting the staff size::
+* Score layout::
+@end menu
+
+@node Setting the staff size
+@subsection Setting the staff size
+
+@untranslated
+
+
+@c index font size, setting
+@c index staff size, setting
+@quotation
+@c modern rental material?
+@end quotation
+@c ode{fontSize} and the layout property @code{staff-space} (in
+@ref{Selecting notation font size}.
+@c ode{layout-set-staff-size} does not change the distance between the
+@node Score layout
+@subsection Score layout
+
+@untranslated
+
+
+@ref{Changing context default settings}.
+@node Breaks
+@section Breaks
+
+@untranslated
+
+
+@menu
+* Line breaking::
+* Page breaking::
+* Optimal page breaking::
+* Optimal page turning::
+* Minimal page breaking::
+* Explicit breaks::
+* Using an extra voice for breaks::
+@end menu
+
+@node Line breaking
+@subsection Line breaking
+
+@untranslated
+
+
+@c index line breaks
+@c index breaking lines
+@c ode{\break}. This will force a line break at this point. However,
+@c TODO Check and add para on default for ragged-right
+@c index regular line breaks
+@c index four bar music.
+@c TODO Check this
+@c ode{\break},
+@c ode{\noBreak}.
+@c ode{\override Beam #'breakable = ##t}.
+@node Page breaking
+@subsection Page breaking
+
+@untranslated
+
+
+@c ode{\pageBreak} or @code{\noPageBreak} commands. These commands are
+@c ode{ragged-last} which have the same effect on vertical spacing:
+@c ode{ragged-bottom} and @code{ragged-last-bottom}. If set to
+@c ode{##t} the systems on all pages or just the last page
+@c ode{ly:optimal-breaking}, @code{ly:page-turn-breaking} and
+@c ode{ly:minimal-breaking}. The default is @code{ly:optimal-breaking},
+@c ode{\pageBreak},
+@c ode{\noPageBreak}.
+@node Optimal page breaking
+@subsection Optimal page breaking
+
+@untranslated
+
+
+@c ode{ly:page-turn-breaking}, it has no concept of page turns.
+@node Optimal page turning
+@subsection Optimal page turning
+
+@untranslated
+
+
+@c ode{\allowPageTurn} will be inserted at the final @q{special} bar line in
+@c ode{minimumPageTurnLength} to determine how long a note-free section must
+@c ode{minimumPageTurnLength} is @code{#(ly:make-moment 1 1)}. If you want
+@c ode{minimumRepeatLengthForPageTurn} then the @code{Page_turn_engraver} will
+@c ode{\allowPageTurn}, may also be used at top-level, between scores and
+@c ode{\pageTurn},
+@c ode{\noPageTurn},
+@c ode{\allowPageTurn}.
+@node Minimal page breaking
+@subsection Minimal page breaking
+
+@untranslated
+
+
+@node Explicit breaks
+@subsection Explicit breaks
+
+@untranslated
+
+
+@c ode{page-break-permission} is overridden to false, Lily will insert
+@node Using an extra voice for breaks
+@subsection Using an extra voice for breaks
+
+@untranslated
+
+
+@c ode{line-break-system-details} and the other useful but long properties of
+@c ode{NonMusicalPaperColumnGrob}, as explained in @ref{Vertical spacing}.
+@ref{Vertical spacing}.
+@node Vertical spacing
+@section Vertical spacing
+
+@untranslated
+
+
+@c index vertical spacing
+@c index spacing, vertical
+@menu
+* Vertical spacing inside a system::
+* Vertical spacing between systems::
+* Explicit staff and system positioning::
+* Two-pass vertical spacing::
+* Vertical collision avoidance::
+@end menu
+
+@node Vertical spacing inside a system
+@subsection Vertical spacing inside a system
+
+@untranslated
+
+
+@c index distance between staves
+@c index staff distance
+@c index space between staves
+@c index space inside systems
+@c ode{max-stretch} is set to zero, disabling stretching. To enable
+@c ode{keep-fixed-while-stretching} property of
+@c ode{VerticalAlignment} object. The context parameters
+@c @lsr{spacing,page-spacing.ly},
+@c @lsr{spacing,alignment-vertical-spacing.ly}.
+@node Vertical spacing between systems
+@subsection Vertical spacing between systems
+
+@untranslated
+
+
+@c ode{page-limit-inter-system-space} variable in the @code{\paper}
+@c ode{1.3} means that the space can be 30% larger than what it would be
+@c ode{1}, the spacing would the same as on a ragged-bottom page, like
+@node Explicit staff and system positioning
+@subsection Explicit staff and system positioning
+
+@untranslated
+
+
+@c ode{NonMusicalPaperColumn #'line-break-system-details}. Where
+@c ode{VerticalAxisGroup} and @code{\paper} settings specify vertical padding,
+@c ode{NonMusicalPaperColumn #'line-break-system-details} specifies exact
+@c ode{NonMusicalPaperColumn #'line-break-system-details} accepts an associative
+@c ode{\override} command in @code{\context} blocks and in the
+@c ode{\with} block. On the other hand, when we override
+@c ode{NonMusicalPaperColumn} in the middle of note entry,
+@c ode{\overrideProperty} command:
+@c \book { } is required in these examples to ensure the spacing
+@c overrides can be seen between systems. -np
+@c ode{line-break-system-details} attribute of the
+@c ode{NonMusicalPaperColumn} grob. Though the
+@c ode{line-break-system-details} attribute alist accepts many
+@c ode{X-offset} pair), we need only set the @code{Y-offset} and
+@c ode{alignment-offsets} pairs to control the vertical startpoint of
+@c ode{Y-offset} and @code{alignment-offsets} are interpreted as multiples
+@node Two-pass vertical spacing
+@subsection Two-pass vertical spacing
+
+@untranslated
+
+
+@quotation
+@end quotation
+@node Vertical collision avoidance
+@subsection Vertical collision avoidance
+
+@untranslated
+
+
+@c ode{outside-staff-priority} tells LilyPond in which order the objects
+@c ode{outside-staff-priority} (in increasing order). One by one, LilyPond
+@c ode{outside-staff-padding}.
+@node Horizontal spacing
+@section Horizontal spacing
+
+@untranslated
+
+
+@c index horizontal spacing
+@c index spacing, horizontal
+@menu
+* Horizontal spacing overview::
+* New spacing area::
+* Changing horizontal spacing::
+* Line length::
+* Proportional notation::
+@end menu
+
+@node Horizontal spacing overview
+@subsection Horizontal spacing overview
+
+@untranslated
+
+
+@c ode{shortest-duration-space} in the @rinternals{SpacingSpanner}
+@c ode{spacing-increment}) of space to the note.
+@c ode{shortest-duration-space} is set to 2.0, meaning that the
+@c ode{spacing-increment}) of horizontal space. This space is counted
+@c ode{lilypond} with the @code{--verbose} option.
+@c ode{common-shortest-duration} in @rinternals{SpacingSpanner}, then
+@c (see @rlearning{Engraving}),
+@c ode{stem-spacing-correction} property in the
+@node New spacing area
+@subsection New spacing area
+
+@untranslated
+
+
+@c ode{newSpacingSection}. This is useful when there are
+@c ode{SpacingSpanner} object, and hence new @code{\override}s
+@node Changing horizontal spacing
+@subsection Changing horizontal spacing
+
+@untranslated
+
+
+@c ode{base-shortest-duration} property. Here
+@c ode{Score.SpacingSpanner #'uniform-stretching}. This
+@node Line length
+@subsection Line length
+
+@untranslated
+
+
+@c index page breaks
+@c index breaking pages
+@c Although line-width can be set in \layout, it should be set in paper
+@c block, to get page layout right.
+@c Setting indent in \paper block makes not much sense, but it works.
+@c Bit verbose and vague, use examples?
+@c ode{line-width}. They are set in the @code{\layout} block. They
+@c index page layout
+@c index vertical spacing
+@c Note that for text there are several options for the last line.
+@c While Knuth TeX uses natural length, lead typesetters use the same
+@c stretch as the previous line. eTeX uses \lastlinefit to
+@c interpolate between both these solutions.
+@node Proportional notation
+@subsection Proportional notation
+
+@untranslated
+
+
+@c ode{\context} block, or directly in music entry
+@c ode{#(ly:make-moment 1 16)}, @code{#(ly:make-moment 1 8)}, and
+@c ode{#(ly:make-moment 3 97)} are all possible as well.
+@c ode{proportionalNotationDuration}? Usually by a process of trial and error,
+@c ode{SpacingSpanner}.
+@c ode{\newSpacingSection}. See @ref{New spacing area}, for more info.
+@ref{New spacing area}.
+@node Fitting music onto fewer pages
+@section Fitting music onto fewer pages
+
+@untranslated
+
+
+@ref{Displaying spacing}.
+@menu
+* Displaying spacing::
+* Changing spacing::
+@end menu
+
+@node Displaying spacing
+@subsection Displaying spacing
+
+@untranslated
+
+
+@c index spacing, display of layout
+@c ode{annotate-spacing} in the @code{\paper} block:
+@c need to have \book{} otherwise we get the separate systems. -hwn
+@c ode{staff-spaces}, and the @code{staff-size} is 20 points (the
+@c ode{staff-spaces} is equivalent to 105 millimeters, the height
+@ref{Setting the staff size}.
+@node Changing spacing
+@subsection Changing spacing
+
+@untranslated
+
+
+@ref{Page formatting},
+@ref{Changing horizontal spacing}.
+
+@c -- SKELETON FILE --
--- /dev/null
+\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
+@c This file is part of notation.tely
+@ignore
+ Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
+
+
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c \version "2.12.0"
+@node Specialist notation
+@chapter Specialist notation
+
+@untranslated
+
+
+@menu
+* Vocal music::
+* Keyboard and other multi-staff instruments::
+* Unfretted string instruments::
+* Fretted string instruments::
+* Percussion::
+* Wind instruments::
+* Chord notation::
+* Ancient notation::
+* World music::
+@end menu
+
+@include notation/vocal.itely
+@include notation/keyboards.itely
+@include notation/unfretted-strings.itely
+@include notation/fretted-strings.itely
+@include notation/percussion.itely
+@include notation/wind.itely
+@include notation/chords.itely
+@include notation/ancient.itely
+@include notation/world.itely
+
+@c -- SKELETON FILE --
--- /dev/null
+depth=../../..
+
+EXTRA_DIST_FILES=$(call src-wildcard,*.texidoc)
+
+include $(depth)/make/stepmake.make
--- /dev/null
+ <p><i>Dernière mise à jour Fri Jul 17 16:08:17 UTC 2009
+</i></p>
+<html>
+<!-- This page is automatically generated by translation-status.py from
+translations.template.html.in; DO NOT EDIT !-->
+<!--
+ Translation of GIT committish: 148e80b8992a7fb9d59ec439c00b79decbbe3bad
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+!-->
+<head>
+ <title>État de la traduction de la documentation de LilyPond</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+<p><a href="index.html">Retour à l'accueil de la documentation</a></p>
+
+<h1>Avancement de la traduction de la documentation</h1>
+
+<p>Cette page présente pour chaque partie de la documentation de
+ LilyPond @TOPLEVEL_VERSION@ l'avancement de la traduction
+ francophone. Pour chaque partie sont indiqués le nombre de mots de
+ l'original en anglais, les noms des traducteurs et relecteurs,
+ le proportion de matériel traduit, l'état de mise à jour, et
+ l'indicateur de révision par rapport au Grand Documentation Project
+ (GDP).
+</p>
+
+<p>Au cours du GDP, la documentation en anglais a été complètement
+ remaniée, et sa révision se poursuit encore actuellement ; le rythme
+ de cette révision ne permet pas de maintenir toutes les traductions
+ à jour. Cependant, le fait que certaines traductions ne soient pas
+ du tout à jour (avec une indication sur fond rouge) ne signifie
+ pas qu'elles sont périmées, mais simplement qu'elles
+ n'atteignent pas la qualité de la documentation en anglais récemment
+ remaniée : les traducteurs font de leur mieux pour au moins mettre à
+ jour dans la documentation la syntaxe et les noms de commande
+ LilyPond. La mise à jour des traductions après le GDP est en
+ cours ; vous pouvez accélérer et améliorer ce processus en
+ participant aux traductions et relectures, qui sont organisées sur
+ la liste de diffusion
+ <a href="http://lists.gnu.org/mailman/listinfo/lilypond-user-fr">lilypond-user-fr@gnu.org</a>.
+</p>
+
+<table align="center" border="2">
+ <tr align="center">
+ <th>GNU LilyPond --- Manuel d'initiation</th> <th>Traducteurs</th>
+ <th>Relecteurs</th>
+ <th>Traduit</th>
+ <th>À jour</th>
+ <th>Autres informations</th>
+ </tr>
+ <tr align="left">
+ <td>Titre des chapitres<br>(429)</td>
+ <td>John Mandereau<br>
+ Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #47ff24">partiellement</span></td>
+ <td>post-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>Préface<br>(411)</td>
+ <td>Valentin Villenave</td>
+ <td>Ludovic Sardain<br>
+ Damien Heurtebise</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1 Introduction<br>(3866)</td>
+ <td>Ludovic Sardain<br>
+ John Mandereau</td>
+ <td>Jean-Charles Malahieude<br>
+ Jean-Yves Baudais<br>
+ Damien Heurtebise</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #40fe23">partiellement</span></td>
+ <td>post-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2 Tutoriel<br>(6368)</td>
+ <td>Nicolas Grandclaude<br>
+ Ludovic Sardain<br>
+ Gauvain Pocentek</td>
+ <td>Jean-Charles Malahieude<br>
+ Valentin Villenave<br>
+ John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #33ff21">partiellement</span></td>
+ <td>post-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>3 Concepts fondamentaux<br>(10323)</td>
+ <td>Valentin Villenave<br>
+ Jean-Charles Malahieude</td>
+ <td>John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td>post-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>4 Retouche de partition<br>(14834)</td>
+ <td>Valentin Villenave<br>
+ Nicolas Klutchnikoff<br>
+ Damien Heurtebise</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #25fe1f">partiellement</span></td>
+ <td>post-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>5 Travail sur des projets LilyPond<br>(5033)</td>
+ <td>Ludovic Sardain</td>
+ <td>Jean-Yves Baudais<br>
+ Valentin Villenave<br>
+ John Mandereau<br>
+ Jean-Charles Malahieude</td>
+ <td><span style="background-color: #dfef77">partiellement (53 %)</span></td>
+ <td><span style="background-color: #e8fe39">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>A Modèles<br>(498)</td>
+ <td></td>
+ <td></td>
+ <td><span style="background-color: #dfef77">partiellement (12 %)</span></td>
+ <td></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>B Tutoriel Scheme<br>(1222)</td>
+ <td></td>
+ <td></td>
+ <td><span style="background-color: #d0f0f8">non</span></td>
+ <td></td>
+ <td>pré-GDP</td>
+ </tr>
+</table>
+<p></p>
+
+<table align="center" border="2">
+ <tr align="center">
+ <th>GNU LilyPond --- Utilisation du programme</th> <th>Traducteurs</th>
+ <th>Relecteurs</th>
+ <th>Traduit</th>
+ <th>À jour</th>
+ <th>Autres informations</th>
+ </tr>
+ <tr align="left">
+ <td>Titre des chapitres<br>(407)</td>
+ <td>John Mandereau<br>
+ Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #47ff24">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1 Installation<br>(193)</td>
+ <td>John Mandereau</td>
+ <td>Jean-Charles Malahieude</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #ff9a4e">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2 Environnement de travail<br>(1149)</td>
+ <td>Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>3 Exécution de LilyPond<br>(3023)</td>
+ <td></td>
+ <td></td>
+ <td><span style="background-color: #d0f0f8">non</span></td>
+ <td></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>4 @command{lilypond-book} : association musique-texte<br>(3248)</td>
+ <td></td>
+ <td></td>
+ <td><span style="background-color: #d0f0f8">non</span></td>
+ <td></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>5 Conversion à partir d'autres formats<br>(1171)</td>
+ <td>Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td>pré-GDP</td>
+ </tr>
+</table>
+<p></p>
+
+<table align="center" border="2">
+ <tr align="center">
+ <th>GNU LilyPond --- Manuel d'initiation</th> <th>Traducteurs</th>
+ <th>Relecteurs</th>
+ <th>Traduit</th>
+ <th>À jour</th>
+ <th>Autres informations</th>
+ </tr>
+ <tr align="left">
+ <td>Titre des chapitres<br>(724)</td>
+ <td>John Mandereau<br>
+ Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #dfef77">partiellement (88 %)</span></td>
+ <td><span style="background-color: #40fe23">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1 Notation musicale générale<br>(91)</td>
+ <td>John Mandereau<br>
+ Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #2cff20">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1.1 Hauteurs<br>(3155)</td>
+ <td>Frédéric Chiasson</td>
+ <td>Valentin Villenave<br>
+ Jean-Charles Malahieude</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #25fe1f">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1.2 Rythme<br>(4757)</td>
+ <td>Frédéric Chiasson<br>
+ Jean-Charles Malahieude</td>
+ <td>Valentin Villenave<br>
+ Jean-Charles Malahieude<br>
+ </td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1.3 Signes d'interprétation<br>(1392)</td>
+ <td>Valentin Villenave</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #ff6f57">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1.4 Répétitions et reprises<br>(555)</td>
+ <td>Valentin Villenave</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #ff6d58">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1.5 Notes simultanées<br>(1456)</td>
+ <td>Frédéric Chiasson<br>
+ Valentin Villenave</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #ff6d58">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1.6 Notation sur la portée<br>(1689)</td>
+ <td>Valentin Villenave<br>
+ Jean-Charles Malahieude</td>
+ <td>John Mandereau</td>
+ <td><span style="background-color: #dfef77">partiellement (69 %)</span></td>
+ <td><span style="background-color: #ff6f57">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1.7 Notation éditoriale<br>(919)</td>
+ <td>Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #ff6f57">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>1.8 Texte<br>(2412)</td>
+ <td>Jean-Charles Malahieude</td>
+ <td>Valentin Villenave<br>
+ John Mandereau</td>
+ <td><span style="background-color: #dfef77">partiellement (97 %)</span></td>
+ <td><span style="background-color: #ff6f57">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2 Notation spécialisée<br>(76)</td>
+ <td>John Mandereau<br>
+ Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #2cff20">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.1 Musique vocale<br>(2725)</td>
+ <td>Valentin Villenave</td>
+ <td>Jean-Charles Malahieude</td>
+ <td><span style="background-color: #dfef77">partiellement (55 %)</span></td>
+ <td><span style="background-color: #ff6d58">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.2 Instruments utilisant des portées multiples<br>(747)</td>
+ <td>Valentin Villenave<br>
+ Jean-Charles Malahieude</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #25fe1f">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.3 Cordes non frettées<br>(235)</td>
+ <td>Valentin Villenave<br>
+ Matthieu Jacquot</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.4 Instruments à cordes frettées<br>(1879)</td>
+ <td>Matthieu Jacquot</td>
+ <td>Jean-Charles Malahieude</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #25fe1f">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.5 Percussions<br>(810)</td>
+ <td>Valentin Villenave</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #dfef77">partiellement (44 %)</span></td>
+ <td><span style="background-color: #ff6d58">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.6 Instruments à vent<br>(136)</td>
+ <td>Valentin Villenave</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.7 Notation des accords<br>(1516)</td>
+ <td>Valentin Villenave</td>
+ <td>Jean-Charles Malahieude<br>
+ John Mandereau</td>
+ <td><span style="background-color: #dfef77">partiellement (59 %)</span></td>
+ <td><span style="background-color: #ff6f57">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.8 Notations anciennes<br>(4487)</td>
+ <td>John Mandereau<br>
+ Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #dfef77">partiellement (82 %)</span></td>
+ <td><span style="background-color: #ff6d58">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>2.9 Musiques du monde<br>(1115)</td>
+ <td></td>
+ <td></td>
+ <td><span style="background-color: #d0f0f8">non</span></td>
+ <td></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>3 Généralités en matière d'entrée et sortie<br>(6170)</td>
+ <td>Jean-Charles Malahieude<br>
+ Valentin Villenave</td>
+ <td></td>
+ <td><span style="background-color: #dfef77">partiellement (5 %)</span></td>
+ <td><span style="background-color: #ff8353">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>4 Gestion de l'espace<br>(8663)</td>
+ <td>Frédéric Chiasson<br>
+ Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #dfef77">partiellement (18 %)</span></td>
+ <td><span style="background-color: #fff23f">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>5 Modification des réglages prédéfinis<br>(11800)</td>
+ <td>Valentin Villenave</td>
+ <td>Gilles Thibault</td>
+ <td><span style="background-color: #dfef77">partiellement (45 %)</span></td>
+ <td><span style="background-color: #ff954f">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>6 Interfaces pour les programmeurs<br>(5187)</td>
+ <td>Valentin Villenave</td>
+ <td>Gilles Thibault</td>
+ <td><span style="background-color: #dfef77">partiellement (9 %)</span></td>
+ <td><span style="background-color: #83fe2c">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>A Bibliographie<br>(310)</td>
+ <td></td>
+ <td></td>
+ <td><span style="background-color: #d0f0f8">non</span></td>
+ <td></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>B Tables du manuel de notation<br>(611)</td>
+ <td>Frédéric Chiasson<br>
+ Jean-Charles Malahieude</td>
+ <td></td>
+ <td><span style="background-color: #dfef77">partiellement (12 %)</span></td>
+ <td><span style="background-color: #97ff2f">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+ <tr align="left">
+ <td>C Aide-mémoire<br>(252)</td>
+ <td>Valentin Villenave</td>
+ <td></td>
+ <td><span style="background-color: #1fff1f">oui</span></td>
+ <td><span style="background-color: #33ff21">partiellement</span></td>
+ <td>pré-GDP</td>
+ </tr>
+</table>
+<p></p>
+
+</body>
+</html>
--- /dev/null
+<html>
+<!--
+ Translation of GIT committish: 148e80b8992a7fb9d59ec439c00b79decbbe3bad
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+!-->
+<head>
+ <title>État de la traduction de la documentation de LilyPond</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+<p><a href="index.html">Retour à l'accueil de la documentation</a></p>
+
+<h1>Avancement de la traduction de la documentation</h1>
+
+<p>Cette page présente pour chaque partie de la documentation de
+ LilyPond @TOPLEVEL_VERSION@ l'avancement de la traduction
+ francophone. Pour chaque partie sont indiqués le nombre de mots de
+ l'original en anglais, les noms des traducteurs et relecteurs,
+ le proportion de matériel traduit, l'état de mise à jour, et
+ l'indicateur de révision par rapport au Grand Documentation Project
+ (GDP).
+</p>
+
+<p>Au cours du GDP, la documentation en anglais a été complètement
+ remaniée, et sa révision se poursuit encore actuellement ; le rythme
+ de cette révision ne permet pas de maintenir toutes les traductions
+ à jour. Cependant, le fait que certaines traductions ne soient pas
+ du tout à jour (avec une indication sur fond rouge) ne signifie
+ pas qu'elles sont périmées, mais simplement qu'elles
+ n'atteignent pas la qualité de la documentation en anglais récemment
+ remaniée : les traducteurs font de leur mieux pour au moins mettre à
+ jour dans la documentation la syntaxe et les noms de commande
+ LilyPond. La mise à jour des traductions après le GDP est en
+ cours ; vous pouvez accélérer et améliorer ce processus en
+ participant aux traductions et relectures, qui sont organisées sur
+ la liste de diffusion
+ <a href="http://lists.gnu.org/mailman/listinfo/lilypond-user-fr">lilypond-user-fr@gnu.org</a>.
+</p>
+
+</body>
+</html>
--- /dev/null
+# translation of LilyPond documentation
+# Copyright (C) 2006 Han-Wen Nienhuys, Jan Nieuwenhuizen
+# This file is distributed under the same license as the lilypond package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2009-08-12 12:33+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. -*- coding: utf-8 -*-
+msgid "Up:"
+msgstr ""
+
+msgid "Next:"
+msgstr ""
+
+msgid "Previous:"
+msgstr ""
+
+msgid "Appendix "
+msgstr ""
+
+msgid "Footnotes"
+msgstr ""
+
+msgid "Table of Contents"
+msgstr ""
fr = LanguageDef ('fr', 'français', double_punct_char_sep=' ', html_filter = french_html_filter)
es = LanguageDef ('es', 'español')
de = LanguageDef ('de', 'deutsch')
+nl = LanguageDef ('nl', 'nederlands')
ja = LanguageDef ('ja', '日本語', enable_ly_identifier_l10n=False)
# Outdated or broken translations may be disabled
# (please run 'make doc-clean' before doing that):
#fr.enabled = False
-LANGUAGES = (site, fr, es, de, ja)
+LANGUAGES = (site, fr, es, de, nl, ja)
if __name__ == '__main__':
print ' '.join ([l.code for l in LANGUAGES if l.enabled and l.code != 'en'])
projects / lilypond.git / commitdiff