lines.
@multitable @columnfractions .1 .3 .3 .3
-@item @tab
+@item @tab
@iftex
@image{henle-flat-bw,4cm}
@end iftex
<img src=lily-flat-bw.png>
@end html
-@item
+@item @tab
Henle (2000)
@tab
B@"{a}renreiter (1950)
Producing good engraving requires skill and knowledge. As the
previous examples show, there is a lot of subtlety involved in music
engraving, and unfortunately, only a small fraction of these details
-are documented. Master engraver must learn all these details from
+are documented. Master engravers must learn all these details from
experience or from other engravers, which is why it takes so long to
become a master. As an engraver gets older and wiser, he will be able
to produce better and more complex pieces. A similar situation is
This has an important implication for the design of the program: at
any time, almost every piece of formatting code must be considered as
temporary. When the need arises, it is to be replaced a solution that
-will cover even more cases. is A ``plug-in'' architecture is a clean
+will cover even more cases. A ``plug-in'' architecture is a clean
way to accomplish this. This is an architecture where new pieces of
code can be inserted in the program dynamically. In such a program, a
new solution can be developed along-side the existing code. For
@lilypond
\score { \notes \relative c'' {
\stemUp
- a4^\f f8
+ a4^\f f'8
}
\paper { raggedright = ##t }
}
\score { \notes \relative c'' {
\stemUp
\once\property Voice. DynamicLineSpanner \override #'padding = #4.0
- a4^\f f8
+ a4^\f f'8
}
\paper { raggedright = ##t }
}
@end lilypond
The glyph of the breath mark can be tweaked by overriding the
-@code{text} property of the @code{BreathingSign} layout object with the name of
-any glyph of @ref{The Feta font}. For example,
+@code{text} property of the @code{BreathingSign} layout object with
+any markup text. For example,
@lilypond[fragment,verbatim,relative]
c'4
-\property Voice.BreathingSign \override #'text = #"scripts-rvarcomma"
+\property Voice.BreathingSign \override #'text
+ = #(make-musicglyph-markup "scripts-rvarcomma")
\breathe
d4
@end lilypond
g4
}
@end lilypond
+
+@noindent
The overrides should also be reverted inside the grace section.
If the layout of grace sections must be changed throughout the music,
@end lilypond
In the above example the music was transformed using the list @code{'drums}.
-Currently the following lists are defined in @file{scm/drums.scm}:
+The following lists are defined in @file{scm/drums.scm}:
@table @code
@item 'drums
to typeset a typical drum kit on a five-line staff:
each staff. The range is graphically specified by two noteheads, that
represent the minimum and maximum pitch. Some publishers use a textual
notation: they put the range in words in front of the corresponding
-staff. LilyPond currently only supports the graphical ambitus notation.
+staff. LilyPond only supports the graphical ambitus notation.
To apply, add the @internalsref{Ambitus_engraver} to the
@internalsref{Voice} context, i.e.
Support for ancient notation is still under heavy development.
Regardless of all of the current limitations (see the bugs section
-below for details), it currently includes features for mensural
+below for details), it includes features for mensural
notation and Gregorian Chant notation. There is also limited support
for figured bass notation.
Accidentals must not be printed within a ligature, but instead need to
be collected and printed in front of it.
-Augmentum dots within ligatures are currently not handled correctly.
+Augmentum dots within ligatures are not handled correctly.
@node Ancient note heads
@syntax
Use the @code{style} property of grob @internalsref{Accidental} to
-select ancient accidentals. Currently supported styles are
+select ancient accidentals. Supported styles are
@code{mensural}, @code{vaticana}, @code{hufnagel} and @code{medicaea}.
@lilypond[singleline,26pt]
@syntax
Use the @code{style} property of grob @internalsref{Rest} to select
-ancient accidentals. Currently supported styles are @code{classical},
+ancient accidentals. Supported styles are @code{classical},
@code{neo_mensural} and @code{mensural}. @code{classical} differs
from the @code{default} style only in that the quarter rest looks like
a horizontally mirrored 8th rest. The @code{neo_mensural} style suits
Use the @code{flag-style} property of grob @internalsref{Stem} to
select ancient flags. Besides the @code{default} flag style,
-currently only @code{mensural} style is supported:
+ only @code{mensural} style is supported:
@lilypond[fragment,singleline,verbatim]
\property Voice.Stem \set #'flag-style = #'mensural
@syntax
-There is limited support for mensural time signatures. Currently, the
+There is limited support for mensural time signatures. The
glyphs are hard-wired to particular time fractions. In other words,
to get a particular mensural signature glyph with the @code{\time n/m}
command, @code{n} and @code{m} have to be chosen according to the
@end lilypond
Use the @code{style} property of grob @internalsref{TimeSignature} to
-select ancient time signatures. Currently supported styles are
+select ancient time signatures. Supported styles are
@code{neo_mensural} and @code{mensural}. The above table uses the
@code{neo_mensural} style. This style is appropriate e.g. for the
incipit of transcriptions of mensural pieces. The @code{mensural}
@refbugs
-Mensural signature glyphs are currently mapped to time fractions in a
+Mensural signature glyphs are mapped to time fractions in a
hard-wired way. This mapping is sensible, but still arbitrary: given
a mensural time signature, the time fraction represents a modern meter
that usually will be a good choice when transcribing a mensural piece
mapping may be unsatisfactory. In particular, the mapping assumes a
fixed transcription of durations (e.g. brevis = half note in 2/2,
i.e. 4:1). Some glyphs (such as the alternate glyph for 6/8 meter)
-are currently not at all accessible through the @code{\time} command.
+are not at all accessible through the @code{\time} command.
Mensural time signatures are supported typographically, but not yet
-musically. The internal representation of durations is currently
+musically. The internal representation of durations is
based on a purely binary system; a ternary division such as 1 brevis =
3 semibrevis (tempus perfectum) or 1 semibrevis = 3 minima (cum
prolatione maiori) is not correctly handled: event times in ternary
To select a specific style of ligatures, a proper ligature engraver
has to be added to the @internalsref{Voice} context, as explained in
-the following subsections. Currently, only white mensural ligatures
+the following subsections. Only white mensural ligatures
are supported with certain limitations. Support for Editio Vaticana
will be added in the future.
@cindex White mensural ligatures
There is limited support for white mensural ligatures. The
-implementation is still experimental; it currently may output strange
+implementation is still experimental; it may output strange
warnings or even crash in some cases or produce weird results on more
complex ligatures.
projects / lilypond.git / commitdiff