@c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+ Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+ When revising a translation, copy the HEAD committish of the
+ version that you are working on. See TRANSLATION for details.
+@end ignore
@node Ancient notation
@section Ancient notation
figured bass notation.
Many graphical objects provide a @code{style} property, see
-@itemize @bullet
+@itemize
@item
@ref{Ancient note heads},
@item
notation flavor without the need for introducing any new notational
concept.
-In addition to the standard articulation signs described in section
-@ref{Articulations}, specific articulation signs for ancient notation
-are provided.
+In addition to the standard articulation signs described in
+section @ref{Articulations and ornamentations}, specific
+articulation signs for ancient notation are provided.
-@itemize @bullet
+@itemize
@item
@ref{Ancient articulations}
@end itemize
adding articulation signs. Some notational concepts are introduced
specifically for ancient notation,
-@itemize @bullet
+@itemize
@item
@ref{Custodes},
@item
contexts. Use them to set up predefined style-specific voice and
staff contexts, and directly go ahead with the note entry,
-@itemize @bullet
+@itemize
@item
@ref{Gregorian Chant contexts},
@item
There is limited support for figured bass notation which came
up during the baroque period.
-@itemize @bullet
+@itemize
@item
@ref{Figured bass}
@end itemize
-Here are all subtopics at a glance:
+@c Here are all subtopics at a glance:
@menu
-* Ancient TODO::
+* Alternative note signs for ancient music::
+* Additional note signs for ancient music::
+* Pre-defined contexts::
+* Musica ficta accidentals::
+* Figured bass::
@end menu
-@node Ancient TODO
-@subsection Ancient TODO
-
-
+@node Alternative note signs for ancient music
+@subsection Alternative note signs for ancient music
@menu
* Ancient note heads::
* Ancient clefs::
* Ancient flags::
* Ancient time signatures::
-* Ancient articulations::
-* Custodes::
-* Divisiones::
-* Ligatures::
-* White mensural ligatures::
-* Gregorian square neumes ligatures::
-* Gregorian Chant contexts::
-* Mensural contexts::
-* Musica ficta accidentals::
-* Figured bass::
@end menu
@node Ancient note heads
-@unnumberedsubsubsec Ancient note heads
+@subsubsection Ancient note heads
@cindex note heads, ancient
@node Ancient accidentals
-@unnumberedsubsubsec Ancient accidentals
+@subsubsection Ancient accidentals
@cindex accidentals
@lilypond[quote,ragged-right,staffsize=26]
\score {
{
- \fatText
+ \textLengthOn
s^\markup {
\column {
"vaticana"
As shown, not all accidentals are supported by each style. When
trying to access an unsupported accidental, LilyPond will switch to a
different style, as demonstrated in
-@lsr{ancient,ancient-accidentals.ly}.
+@c @lsr{ancient,ancient-accidentals.ly}.
Similarly to local accidentals, the style of the key signature can be
controlled by the @code{glyph-name-alist} property of the
@seealso
-In this manual: @ref{Pitches}, @ref{Cautionary accidentals}, and
+Notation Reference: @ref{Pitches}, @ref{Accidentals}, and
@ref{Automatic accidentals}, give a general introduction of the use of
accidentals. @ref{Key signature}, gives a general introduction of
the use of key signatures.
-Program reference: @internalsref{KeySignature}.
+Internals Reference: @internalsref{KeySignature}.
-Examples: @lsrdir{ancient}
+Examples: @c @lsrdir{ancient}
@node Ancient rests
-@unnumberedsubsubsec Ancient rests
+@subsubsection Ancient rests
@cindex rests, ancient
There are no 32th and 64th rests specifically for the mensural or
neo-mensural style. Instead, the rests from the default style will be
-taken. See @lsr{pitches,rests} for a chart of all rests.
+taken. See @c @lsr{pitches,rests} for a chart of all rests.
There are no rests in Gregorian Chant notation; instead, it uses
@ref{Divisiones}.
@seealso
-In this manual: @ref{Rests}, gives a general introduction into the use of
+Notation Reference: @ref{Rests}, gives a general introduction into the use of
rests.
@node Ancient clefs
-@unnumberedsubsubsec Ancient clefs
+@subsubsection Ancient clefs
@cindex clefs
@seealso
-In this manual: see @ref{Clef}.
+Notation Reference: see @ref{Clef}.
@refbugs
@node Ancient flags
-@unnumberedsubsubsec Ancient flags
+@subsubsection Ancient flags
@cindex flags
scope for mensural notation).
@node Ancient time signatures
-@unnumberedsubsubsec Ancient time signatures
+@subsubsection Ancient time signatures
@cindex time signatures
@lilypond[ragged-right,fragment,relative=1,quote]
{
- \fatText
+ \textLengthOn
\time 2/2
c1^\markup { \hspace #-2.0 \typewriter default }
The @code{old6/8alt} symbol (an alternate symbol for 6/8) is not
addressable with @code{\time}. Use a @code{\markup} instead
+
+@node Additional note signs for ancient music
+@subsection Additional note signs for ancient music
+
+@menu
+* Ancient articulations::
+* Custodes::
+* Divisiones::
+* Ligatures::
+* White mensural ligatures::
+* Gregorian square neumes ligatures::
+@end menu
+
+
@node Ancient articulations
-@unnumberedsubsubsec Ancient articulations
+@subsubsection Ancient articulations
@cindex articulations
-In addition to the standard articulation signs described in section
-@ref{Articulations}, articulation signs for ancient notation are
-provided. These are specifically designed for use with notation in
-Editio Vaticana style.
+In addition to the standard articulation signs described in
+section @ref{Articulations and ornamentations}, articulation signs
+for ancient notation are provided. These are specifically
+designed for use with notation in Editio Vaticana style.
@lilypond[quote,ragged-right,verbatim]
\include "gregorian-init.ly"
the right end of the episem line is often too far to the right.
@node Custodes
-@unnumberedsubsubsec Custodes
+@subsubsection Custodes
@cindex custos
@cindex custodes
@seealso
-Program reference: @internalsref{Custos}.
+Internals Reference: @internalsref{Custos}.
Examples:
-@lsr{ancient,custodes@/.ly}.
+@c @lsr{ancient,custodes@/.ly}.
@node Divisiones
-@unnumberedsubsubsec Divisiones
+@subsubsection Divisiones
@cindex divisio
@cindex divisiones
@seealso
-In this manual: @ref{Breath marks}.
+Notation Reference: @ref{Breath marks}.
-Program reference: @internalsref{BreathingSign}.
+Internals Reference: @internalsref{BreathingSign}.
-Examples: @lsr{expressive,breathing-sign.ly}.
+Examples: @c @lsr{expressive,breathing-sign.ly}.
@node Ligatures
-@unnumberedsubsubsec Ligatures
+@subsubsection Ligatures
@cindex Ligatures
@end menu
@node White mensural ligatures
-@unnumberedsubsubsec White mensural ligatures
+@subsubsection White mensural ligatures
@cindex Mensural ligatures
@cindex White mensural ligatures
Horizontal spacing is poor.
@node Gregorian square neumes ligatures
-@unnumberedsubsubsec Gregorian square neumes ligatures
+@subsubsection Gregorian square neumes ligatures
@cindex Square neumes ligatures
@cindex Gregorian square neumes ligatures
@c Therefore, it should somehow be included rather than duplicated all
@c the time. --jr
-@c why not make identifiers in ly/engraver-init.ly? --hwn
+@c why not make variables in ly/engraver-init.ly? --hwn
@c Because it's just used to typeset plain notes without
@c a staff for demonstration purposes rather than something
unary music function, such that @code{\augmentum} can be intermixed
with head prefixes in arbitrary order.
+
+@node Pre-defined contexts
+@subsection Pre-defined contexts
+
+@menu
+* Gregorian Chant contexts::
+* Mensural contexts::
+@end menu
+
+
@node Gregorian Chant contexts
-@unnumberedsubsubsec Gregorian Chant contexts
+@subsubsection Gregorian Chant contexts
@cindex VaticanaVoiceContext
@cindex VaticanaStaffContext
@node Mensural contexts
-@unnumberedsubsubsec Mensural contexts
+@subsubsection Mensural contexts
@cindex MensuralVoiceContext
@cindex MensuralStaffContext
The predefined @code{MensuralVoiceContext} and
-@code{MensuralStaffContext} can be used to engrave a piece in mensural
-style. These contexts initialize all relevant context properties and
-grob properties to proper values, so you can immediately go ahead
-entering the chant, as the following excerpt demonstrates
+@code{MensuralStaffContext} can be used to engrave a piece in
+mensural style. These contexts initialize all relevant context
+properties and grob properties to proper values, so you can
+immediately go ahead entering the chant, as the following excerpt
+demonstrates
@lilypond[quote,ragged-right,verbatim]
\score {
@end lilypond
@node Musica ficta accidentals
-@unnumberedsubsubsec Musica ficta accidentals
+@subsection Musica ficta accidentals
-In European music from before about 1600, singers were often expected
-to chromatically alter notes at their own initiative. This is called
-@q{Musica Ficta}. In modern transcriptions, these accidentals are
-usually printed over the note.
+In European music from before about 1600, singers were often
+expected to chromatically alter notes at their own initiative.
+This is called @q{Musica Ficta}. In modern transcriptions, these
+accidentals are usually printed over the note.
@cindex Accidental, musica ficta
@cindex Musica ficta
ais bis
@end lilypond
+This will treat @emph{every} subsequent accidentals as
+@emph{musica ficta} until it is unset with @code{\set
+suggestAccidentals = ##f}. A more convenient way is to use
+@code{\once}:
+
+@lilypond[verbatim,fragment,relative=1]
+fis gis
+\once \set suggestAccidentals = ##t
+ais ais bis
+@end lilypond
+
@seealso
-Program reference: @internalsref{Accidental_engraver} engraver and the
-@internalsref{AccidentalSuggestion} object.
+Internals Reference: @internalsref{Accidental_engraver} engraver and
+the @internalsref{AccidentalSuggestion} object.
@node Figured bass
-@unnumberedsubsubsec Figured bass
+@subsection Figured bass
@cindex Basso continuo
@end lilypond
Spaces may be inserted by using @code{_}. Brackets are
-introduced with @code{[} and @code{]}. You can also include text
+introduced with @code{[} and @code{]}. You can also include text
strings and text markups, see @ref{Overview of text markup commands}.
@example
In this case, the extender lines always replace existing figures.
The @code{FiguredBass} context doesn't pay attention to the actual
-bass line. As a consequence, you may have to insert extra figures to
+bass line. As a consequence, you may have to insert extra figures to
get extender lines below all notes, and you may have to add @code{\!}
to avoid getting an extender line, e.g.
@end lilypond
When using continuation lines, common figures are always put in the
-same vertical position. When this is unwanted, you can insert a rest
-with @code{r}. The rest will clear any previous alignment. For
+same vertical position. When this is unwanted, you can insert a rest
+with @code{r}. The rest will clear any previous alignment. For
example, you can write
@example
@seealso
-Program reference: @internalsref{NewBassFigure},
+Internals Reference: @internalsref{NewBassFigure},
@internalsref{BassFigureAlignment}, @internalsref{BassFigureLine},
@internalsref{BassFigureBracket}, and
@internalsref{BassFigureContinuation} objects and
projects / lilypond.git / blobdiff