-@c -*- coding: latin-1; mode: texinfo; -*-
+@c -*- coding: utf-8; mode: texinfo; -*-
@c This file is part of lilypond.tely
@c A menu is needed before every deeper *section nesting of @node's; run
@menu
* Automatic staff changes::
* Manual staff switches::
+* Laissez vibrer ties::
* Pedals::
* Staff switch lines::
* Cross staff stems::
@end menu
-@
-refbugs
+@refbugs
Dynamics are not centered, but workarounds do exist. See the
``piano centered dynamics'' template in @ref{Piano templates}.
@end example
+@node Laissez vibrer ties
+@subsection Laissez vibrer ties
+@cindex Laissez vibrer
+@cindex Ties, laissez vibrer
+
+L.v. ties (laissez vibrer) indicate that notes must not be damped at the
+end. It is used in notation for piano, harp and other string and
+percussion instruments. They can be entered using @code{\laissezVibrer},
+
+@lilypond[fragment,raggedright,verbatim,relative=1]
+<c f g>\laissezVibrer
+@end lilypond
+
+@seealso
+
+Program reference:
+@internalsref{LaissezVibrerTie}
+@internalsref{LaissezVibrerTieColumn}
+
+Example files:
+@inputfileref{input/regression,laissez-vibrer-tie.ly}
+
@node Pedals
@subsection Pedals
@cindex Pedals
c\sostenutoDown d e c, f g a\sostenutoUp
@end lilypond
+@seealso
+
+In this manual: @ref{Laissez vibrer ties}
+
@node Staff switch lines
@subsection Staff switch lines
it with utf-8 encoding. See @ref{Text encoding} for more info.
@example
-\lyricmode @{ He said: âÂ\80Â\9cLet my peo ple goâÂ\80Â\9d. @}
+\lyricmode @{ He said: â\80\9cLet my peo ple goâ\80\9d. @}
@end example
The full definition of a word start in Lyrics mode is somewhat more
{ Ky -- _ _ ri __ _ _ _ e }
@end lilypond
+@subsubsection Spacing lyrics
+
+@cindex Spacing lyrics
+@cindex Lyrics, increasing space between
+
+To increase the space between lyrics, use the @code{SeparationItem}
+property.
+
+@lilypond[relative,verbatim,fragment,quote,raggedright]
+{
+ c c c c
+ \override Score.SeparationItem #'padding = #5
+ c c c c
+}
+\addlyrics {
+ longtext longtext longtext longtext
+ longtext longtext longtext longtext
+}
+@end lilypond
+
+
@node More stanzas
@subsection More stanzas
@node Other vocal issues
@subsection Other vocal issues
-Bagpipe music nominally uses the key of D Major (even though that
-isn't really true). However, since that is the only key that can be used,
-the key signature is normally not written out. To set this up correctly,
-always start your music with @code{\hideKeySignature}. If you for some
-reason want to show the key signature, you can use @code{\showKeySignature}
-instead.
-
@ignore
yeah, I'm giving up somewhat by stuffing a bunch of things in
here. But at least they're in the manual now; it's easier to
notated by cross noteheads. This is demonstrated in
@ref{Special noteheads}.
-Some modern music use cross fingering on c and f to flatten those notes.
-This can be indicated by @code{cflat} or @code{fflat}. Similarly, the
-piobaireachd high g can be written @code{gflat} when it occurs in light
-music.
@node Rhythmic music
@section Rhythmic music
notes in the appropiate octaves, so you do not need to worry about
@code{\relative} or @code{\transpose}.
-@ignore
-@li lypond[raggedright,verbatim,quote,notime]
+@lilypond[raggedright,verbatim,quote,notime]
\include "bagpipe.ly"
{ \grg G4 \grg a \grg b \grg c \grg d \grg e \grg f \grA g A }
-@end lilypo nd
-@end ignore
+@end lilypond
+
+Bagpipe music nominally uses the key of D Major (even though that
+isn't really true). However, since that is the only key that can be used,
+the key signature is normally not written out. To set this up correctly,
+always start your music with @code{\hideKeySignature}. If you for some
+reason want to show the key signature, you can use @code{\showKeySignature}
+instead.
+
+Some modern music use cross fingering on c and f to flatten those notes.
+This can be indicated by @code{cflat} or @code{fflat}. Similarly, the
+piobaireachd high g can be written @code{gflat} when it occurs in light
+music.
+
@node Bagpipe example
@subsection Bagpipe example
This is what the well known tune Amazing Grace looks like in bagpipe
notation.
-@ignore
-@lilyp ond[raggedright,verbatim,quote]
+@lilypond[verbatim,quote]
\include "bagpipe.ly"
\layout {
indent = 0.0\cm
\context { \Score \remove "Bar_number_engraver" }
}
+
\header {
title = "Amazing Grace"
meter = "Hymn"
arranger = "Trad. arr."
}
+
{
\hideKeySignature
\time 3/4
\slurd d2
\bar "|."
}
-@end lilypo nd
-@end ignore
+@end lilypond
+
@node Ancient notation
@section Ancient notation
@c TODO: musicological blurb about FB
-LilyPond has limited support for figured bass
+LilyPond has support for figured bass
@lilypond[quote,raggedright,verbatim,fragment]
<<
\figuremode { < [4 6] 8 [_! 12] > < 5 \markup{ + \number 6 } > }
@end lilypond
+It is also possible to use continuation lines for repeated figures,
+
+@lilypond[verbatim,relative=1]
+<<
+ \new Staff { c4 c }
+ \figures {
+ \set useBassFigureExtenders = ##t
+ <4 6> <3 6> <3 7>
+ }
+>>
+@end lilypond
Although the support for figured bass may superficially resemble chord
-support, it works much simpler. The @code{\figuremode} mode simply
-stores the numbers and @internalsref{FiguredBass} context prints
-them as entered. There is no conversion to pitches and no
-realizations of the bass are played in the MIDI file.
+support, it is much simpler. The @code{\figuremode} mode simply
+stores the numbers and @internalsref{FiguredBass} context prints them
+as entered. There is no conversion to pitches and no realizations of
+the bass are played in the MIDI file.
Internally, the code produces markup texts. You can use any of the
markup text properties to override formatting. For example, the
@seealso
-Program reference: @internalsref{BassFigure} object,
+Program reference: @internalsref{NewBassFigure},
+@internalsref{BassFigureAlignment}, @internalsref{BassFigureLine},
+@internalsref{BassFigureBracket}, and
+@internalsref{BassFigureContinuation} objects and
@internalsref{FiguredBass} context.
@refbugs
projects / lilypond.git / blobdiff