or
@example
-\lilypond@{ YOUR LILYPOND CODE @}
+\lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
@end example
Additionally, @code{\lilypondversion} displays the current version
If a greater number of systems is requested, a @TeX{} conditional must
be used before the @code{\endinput}. In this example, replace @q{2} by
-the number of systems you want in the output,
+the number of systems you want in the output.
@example
\def\betweenLilyPondSystem#1@{
- \ifnum##1<2\else\endinput\fi
+ \ifnum##1<2\else\expandafter\endinput\fi
@}
@end example
+@noindent
+(Since @code{\endinput} immediately stops the processing of the current
+input file we need @code{\expandafter} to delay the call of @code{\endinput}
+after executing @code{\fi} so that the @code{\if}-@code{\fi} clause is
+balanced.)
+
Remember that the definition of @code{\betweenLilyPondSystem} is
effective until @TeX{} quits the current group (such as the @LaTeX{}
environment) or is overridden by another definition (which is, in
@example
\def\onlyFirstNSystems#1@{
- \def\betweenLilyPondSystem##1@{\ifnum##1<#1\else\endinput\fi@}
+ \def\betweenLilyPondSystem##1@{%
+ \ifnum##1<#1\else\expandafter\endinput\fi@}
@}
@end example
@c -*- coding: utf-8; mode: texinfo; documentlanguage: fr -*-
@ignore
- Translation of GIT committish: 95e6825ee09ca7f8eea87580301c8819ff1d571b
+ Translation of GIT committish: 7cf1ff2069f1b0e945d0c0852791b2306451db97
When revising a translation, copy the HEAD committish of the
version that you are working on. See TRANSLATION for details.
La propriété @code{right-padding} joue sur l'espacement entre une
altération et la note sur laquelle elle porte. On ne l'utilise pas
-souvent, mais l'exemple ci-dessous montre une situation où elle est
-nécessaire. Imaginons que nous voulions faire apparaître un accord qui
-contienne à la fois un si bécarre et un si bémol. Pour qu'il n'y ait
-pas de doute, nous chercherions à faire précéder la note d'un signe
-bécarre et d'un signe bémol. Voici différentes tentatives pour y
-parvenir :
-
-@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
-<b bes>
-<b! bes>
-<b? bes>
-@end lilypond
-
-Aucune n'est satifaisante, et la seconde se solde même par une
-collision entre les deux signes.
-
-Une solution pour arriver à nos fins consiste à retoucher le stencil des
-altérations grâce à un markup qui contient les symboles bécarre et
-bémol, dans l'ordre que nous souhaitons, comme ceci :
+souvent, mais l'espacement par défaut peut se révéler inadéquat avec
+certaines altérations ou certains glyphes utilisés en musique
+microtonale. Le stencil de l'altération devra alors être construit sous
+la forme d'un @code{markup} qui contiendra le ou les symboles requis,
+comme ceci :
@cindex Accidental, exemple de dérogation
@cindex text, exemple d'utilisation de la propriété
@cindex right-padding, exemple d'utilisation de la propriété
@lilypond[quote,ragged-right,verbatim]
-naturalplusflat = \markup { \natural \flat }
+sesquisharp = \markup { \sesquisharp }
\relative c'' {
+ c
+ % This prints a sesquisharp but the spacing is too small
+ \once \override Accidental
+ #'stencil = #ly:text-interface::print
+ \once \override Accidental #'text = #sesquisharp
+ cis c
+ % This improves the spacing
+ \once \override Score.AccidentalPlacement #'right-padding = #0.6
\once \override Accidental
#'stencil = #ly:text-interface::print
- \once \override Accidental #'text = #naturalplusflat
- \once \override Score.AccidentalPlacement #'right-padding = #1.5
- <b bes>
+ \once \override Accidental #'text = #sesquisharp
+ cis
}
@end lilypond
qui ne sera pas reprise par la suite. Le type de stencil est
obligatoirement une procédure, qui consiste ici à imprimer le contenu de
la propriété @code{text} de @code{Accidental}, déclaré comme étant un
-signe bécarre suivi d'un signe bémol. Celui-ci est ensuite repoussé
-devant la tête de note par la retouche de @code{right-padding}.
+signe sesqui-dièse. Celui-ci est ensuite repoussé devant la tête de
+note par la retouche de @code{right-padding}.
@noindent
@c -*- coding: utf-8; mode: texinfo; documentlanguage: fr -*-
@ignore
- Translation of GIT committish: 7b70644b95f383b4281e9ffa146d315d2ada11d3
+ Translation of GIT committish: 7cf1ff2069f1b0e945d0c0852791b2306451db97
When revising a translation, copy the HEAD committish of the
version that you are working on. See TRANSLATION for details.
d4 e d c
@end lilypond
+Notez bien que ces commandes prédéfinies affecteront toutes les portées
+de la partition, même si vous ne les placez que dans un simple contexte
+@code{Voice}. Pour éviter ce désagrément, transférez le
+@code{Timing_translator} du contexte @code{Score} au contexte
+@code{Staff}, comme indiqué au chapitre @ref{Notation polymétrique}.
+
@predefined
@code{\cadenzaOn},
@rglos{cadenza}.
Manuel de notation :
-@ref{Visibilité des objets}.
+@ref{Visibilité des objets},
+@ref{Notation polymétrique}.
Morceaux choisis :
@rlsr{Rhythms}.
@item Pedro Kroeger:
Build meister
+@item @uref{http://percival-music.ca, Graham Percival}:
+Documentation editor, Bug meister, Grand Documentation Project
+leader.
+
@item Erik Sandberg:
Bug meister
@warning{If you are happy with the GUI, then please ignore these
instructions.}
-FIXME: once 2.12.4 is out, delete a bunch of this -- IIRC we now
-*do* provide Python, so this stuff gets much easier.
+@ignore
+FIXME: I had one report that we don't need this stuff; will delete
+after confirmation. -gp
@subsubheading Using Python scripts on MacOS 10.3 or 10.4
@example
#!@var{/path/to/newly_installed/python}
@end example
-
+@end ignore
@subsubheading MacOS X on the command line
-The scripts --- such as @command{lilypond-book}, @command{convert-ly},
-@command{abc2ly}, and even @command{lilypond} itself --- are included
-inside the @code{.app} file for MacOS@tie{}X. They can be run from
-the command line by invoking them directly, e.g.
-
-@example
-@var{path/to}/LilyPond.app/Contents/Resources/bin/lilypond
-@end example
+The most convenient way to run lilypond scripts is by setting up
+@qq{helper} scripts of your own.
-@noindent
-The same is true of the other scripts in that directory, including
-@command{lilypond-book}, @command{convert-ly}, @command{abc2ly}, etc.
+@enumerate
-Alternatively, you may create scripts which add the path
-automatically. Create a directory to store these scripts,
+@item
+Create a directory to store these scripts,
@example
mkdir -p ~/bin
cd ~/bin
@end example
-Create a file called @code{lilypond} which contains
-@example
-exec @var{path/to}/LilyPond.app/Contents/Resources/bin/lilypond "$@@"
-@end example
+@item
+Create a file called @command{lilypond} which contains
+
+FIXME: obvious css issues to be dealt with. :(
+@c we need a small font here to fit. -gp
+@smallexample
+exec @var{DIR}/LilyPond.app/Contents/Resources/bin/lilypond "$@@"
+@end smallexample
+
+@warning{@var{DIR} will generally be @code{/Applications/}}
-Create similar files @code{lilypond-book}, @code{convert-ly}, and
-any other helper programs you use (@code{abc2ly}, @code{midi2ly},
-etc). Simply replace the @code{bin/lilypond} with
-@code{bin/convert-ly} (or other program name) in the above file.
+@item
+Create similar files @command{lilypond-book},
+@command{convert-ly}, and any other scripts you wish to use, by
+replacing the @command{bin/lilypond} with @command{bin/convert-ly}
+(or other program name).
+
+
+@item
Make the file executable,
@example
chmod u+x lilypond
@end example
-Now, add this directory to your path. Modify (or create)
-a file called @code{.profile} in your home directory such that it contains
+
+@item
+Now, add this directory to your path. Modify (or create) a file
+called @code{.profile} in your home directory such that it
+contains
@example
export PATH=$PATH:~/bin
@end example
-@noindent
This file should end with a blank line.
-Note that @var{path/to} will generally be @code{/Usages/}.
+@end enumerate
+
+@subsubheading Invoking individual scripts
+
+The scripts --- such as @command{lilypond-book}, @command{convert-ly},
+@command{abc2ly}, and even @command{lilypond} itself --- are included
+inside the @code{.app} file for MacOS@tie{}X.
+
+Scripts can also be run from the command line by invoking them
+directly:
+
+@example
+@var{path/to}/LilyPond.app/Contents/Resources/bin/lilypond
+@end example
+The same is true for all other scripts in that directory, such as
+@command{lilypond-book} and @command{convert-ly}.
@divEnd
\input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
+@c FIXME: dump "public domain" notice in this manual, and fix
+@c the generic doc page title macro to not automatically put
+@c FDL on stuff. Or maybe make a separate macro.
+
@setfilename lilypond-snippets.info
@settitle LilyPond snippets
@documentencoding UTF-8
projects / lilypond.git / commitdiff