Guide, node Updating translation committishes..
@end ignore
-@c \version "2.14.0"
+@c \version "2.16.0"
@node Chord notation
\chordmode { f2 g }
@end lilypond
-
@seealso
Music Glossary:
@rglos{chord}.
Snippets:
@rlsr{Chords}.
-
@knownissues
-
Predefined shorthands for articulations and ornaments cannot be used
on notes in chord mode, see @ref{Articulations and ornamentations}.
}
@end lilypond
+
@node Common chords
@unnumberedsubsubsec Common chords
@end multitable
-
@seealso
Notation Reference:
@ref{Common chord modifiers},
Snippets:
@rlsr{Chords}.
-
@knownissues
Only one quality modifier should be used per chord, typically on the
highest step present in the chord. Chords with more than quality
standard chords are shown in
@ref{Common chord modifiers}.
-
@seealso
Notation Reference:
@ref{Common chord modifiers}.
Snippets:
@rlsr{Chords}.
-
@knownissues
-
Each step can only be present in a chord once. The following
simply produces the augmented chord, since @code{5+} is
interpreted last.
}
@end lilypond
+
@node Displaying chords
@subsection Displaying chords
@cindex chords, suppressing repeated
@funindex chordChanges
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
{showing-chords-at-changes.ly}
-@c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@c @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
@c {adding-bar-lines-to-chordnames-context.ly}
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
{simple-lead-sheet.ly}
-
@seealso
Music Glossary:
@rglos{chord}.
@rinternals{Volta_engraver},
@rinternals{Bar_engraver}.
-
@knownissues
-
Chords containing inversions or altered bass notes are not named
properly if entered using simultaneous music.
options are @code{whiteTriangleMarkup} and
@code{blackTriangleMarkup}.
+@funindex additionalPitchPrefix
+
+@item additionalPitchPrefix
+
+When the chord name contains additional pitches, they can optionally
+be prefixed with some text. The default is no prefix, in order to
+avoid too much visual clutter, but for small numbers of additional
+pitches this can be visually effective.
+
+@lilypond[verbatim,quote,ragged-right]
+\new ChordNames {
+ <c e g d'> % add9
+ \set additionalPitchPrefix = #"add"
+ <c e g d'> % add9
+}
+@end lilypond
+
@funindex chordNoteNamer
@item chordNoteNamer
@item chordNameSeparator
-Different parts of a chord name are normally separated by a slash.
-By setting @code{chordNameSeparator}, you can use any desired markup
-for a separator.
+Different parts of a chord name are normally separated by a small
+amount of horizontal space. By setting @code{chordNameSeparator}, you
+can use any desired markup for a separator. This does not affect the
+separator between a chord and its bass note; to customize that, use
+@code{slashChordSeparator}.
+
+@lilypond[verbatim,quote,ragged-right]
+\chords {
+ c4:7.9- c:7.9-/g
+ \set chordNameSeparator = \markup { "/" }
+ \break
+ c4:7.9- c:7.9-/g
+}
+@end lilypond
+
+@funindex slashChordSeparator
+
+@item slashChordSeparator
+
+Chords can be played over a bass note other than the conventional root
+of the chord. These are known as ``inversions'' or ``slash chords'',
+because the default way of notating them is with a forward slash
+between the main chord and the bass note. Therefore the value of
+@code{slashChordSeparator} defaults to a forward slash, but you can
+change it to any markup you choose.
+
+@lilypond[verbatim,quote,ragged-right]
+\chords {
+ c4:7.9- c:7.9-/g
+ \set slashChordSeparator = \markup { " over " }
+ \break
+ c4:7.9- c:7.9-/g
+}
+@end lilypond
@funindex chordNameExceptions
The second item is a markup that will follow the @code{chordRootNamer}
output to create the chord name.
+@funindex minorChordModifier
+
+@item minorChordModifier
+
+Minor chords are often denoted via a @q{m} suffix to the right of the
+root of the chord. However some idioms prefer other suffices, such as
+a minus sign.
+
+@lilypond[verbatim,quote,ragged-right]
+\chords {
+ c4:min f:min7
+ \set minorChordModifier = \markup { "-" }
+ \break
+ c4:min f:min7
+}
+@end lilypond
+
@funindex chordPrefixSpacer
+
@item chordPrefixSpacer
-The @q{m} for minor chords is usually printed immediately to the
-right of the root of the chord. A spacer can be placed between
-the root and @q{m} by setting @code{chordPrefixSpacer}.
-The spacer is not used when the root is altered.
+The modifier for minor chords as determined by
+@code{minorChordModifier} is usually printed immediately to the right
+of the root of the chord. A spacer can be placed between the root and
+the modifier by setting @code{chordPrefixSpacer}. The spacer is not
+used when the root is altered.
@end table
@snippets
@cindex exceptions, chord names.
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{chord-name-exceptions.ly}
@c TODO - tweak snippet to use \blackTriangleMarkup as well
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{chord-name-major7.ly}
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{adding-bar-lines-to-chordnames-context.ly}
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{volta-below-chords.ly}
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{changing-chord-separator.ly}
-
@seealso
Notation Reference:
@ref{Chord name chart},
Snippets:
@rlsr{Chords}.
-@c Internals Reference:
-@c @r internals{}.
-
-
@knownissues
-
Chord names are determined from both the pitches that are present
in the chord and the information on the chord structure that may
have been entered in @code{\chordmode}. If the simultaneous pitches
@node Figured bass
@subsection Figured bass
-@lilypondfile[quote]{figured-bass-headword.ly}
+@c Line width hack because of instrument names
+@lilypondfile[quote,staffsize=18,line-width=14.5\cm]{figured-bass-headword.ly}
Figured bass notation can be displayed.
@code{baseline-skip}.
@end ignore
-
@seealso
Music Glossary:
@rglos{figured bass}.
@snippets
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{changing-the-positions-of-figured-bass-alterations.ly}
-
@seealso
-@c Music Glossary:
-@c @rglos{}.
-@c
-@c Learning Manual:
-@c @rlearning{}.
-@c
-@c Notation Reference:
-@c @ref{}.
-@c
-@c Application Usage:
-@c @rprogram{}.
-@c
-@c Installed Files:
-@c @file{}.
-@c
Snippets:
@rlsr{Chords}.
@rinternals{FiguredBass}.
-@c @knownissues
-
-
@node Displaying figured bass
@unnumberedsubsubsec Displaying figured bass
>>
@end lilypond
-
@predefined
@cindex figured bass alignment
@code{\bassFigureStaffAlignmentDown},
@code{\bassFigureStaffAlignmentNeutral}.
@endpredefined
-
-@c @snippets
-
-
@seealso
-@c Music Glossary:
-@c @rglos{}.
-@c
-@c Learning Manual:
-@c @rlearning{}.
-@c
-@c Notation Reference:
-@c @ref{}.
-@c
-@c Application Usage:
-@c @rprogram{}.
-@c
-@c Installed Files:
-@c @file{}.
-@c
Snippets:
@rlsr{Chords}.
@rinternals{BassFigureContinuation},
@rinternals{FiguredBass}.
-
@knownissues
-
To ensure that continuation lines work properly, it is
safest to use the same rhythm in the figure line as in
the bass line.
}
>>
@end lilypond
-
projects / lilypond.git / blobdiff