+2004-02-26 Heikki Junes <hjunes@cc.hut.fi>
+
+ * input/test/[a-b]*.ly: refresh descriptions -- avoid referring
+ to a file in printed documentation, instead, refer either to a
+ syntax or to an output.
+
2004-02-26 Jan Nieuwenhuizen <janneke@gnu.org>
* input/regression/beam-center-slope.ly: Add test.
\header {
texidoc= "@cindex Add Stacato
-Using make-music, you can add various stuff to notes. Here
-is an example how to add staccato dots. Note: for this simple case
-one would not use scm constructs. See separate-staccato.ly first.
+Using @code{make-music}, you can add various stuff to notes. In this
+example staccato dots are added to the notes. For this simple case,
+it is not necessary to use scm constructs (see @code{separate-staccato.ly}).
"
}
\header {
texidoc= "@cindex make-music Fingering
-You can add various stuff to notes using make-music.
-Here is an example of how to add an extra fingering.
+You can add various stuff to notes using @code{make-music}.
+In this example, an extra fingering is attached to a note.
-In general, first do a display of the music you want to
-create, then write a function that will build the structure for you.
+In general, first do a @code{display} of the music you want to
+create, then write a function that will structure the music for you.
"
}
\header {
-texidoc = "Ambituses can be switched off or translated by using
-applyoutput.
+texidoc = "The showing of ambituses can be switched off or they can be
+shifted horizontally by using @code{applyoutput}.
If you want to mix per-voice and per-staff ambituses, then you have to
-define you have to declare a new context type derived from the
-@code{Voice} context or @code{Staff} context. The derived context
-must consist of the @code{Ambitus_engraver} and it must be accepted by
-a proper parent context, in the below example the @code{Staff} context
-or @code{Score} context, respectively. The original context and the
-derived context can then be used in parallel in the same score. (this is not demonstrated in this file).
+define new context type derived from the @code{Voice} or @code{Staff}
+context. The derived context must contain the @code{Ambitus_engraver}
+and it must be accepted by a proper parent context, which are respectively
+the @code{Staff} context or @code{Score} context in the example below.
+The original context and the derived context can then be used in parallel
+in the same score (not demonstrated in this file).
"
}
\header {
texidoc = "@cindex Ancient Accidentals
-Accidentals are available in different ancient styles. This
-file lists all of them.
+Accidentals are available in different ancient styles, which all
+are collected here.
"
}
% different locations.
\header {
texidoc = "@cindex Ancient Font
-Here is a display of many (all?) symbols that are
+Here are shown many (all?) of the symbols that are
included in LilyPond's support of ancient notation.
"
}
% for ancient-font.ly
\header {
texidoc="@cindex Ancient Time Signatures
-Should use old style.
+Time signatures may also be engraved in an old style.
"
}
\header {
texidoc = "@cindex Bagpipe Music
-Here's an example of bagpipe music.
+Bagpipe music may contain a lot of grace notes.
"
}
texidoc = "@cindex Bars Always
-By setting @code{barAlways} and @code{defaultBarType,} you can automatically insert barlines everywhere."
+By setting @code{barAlways} and @code{defaultBarType}, barlines may be inserted automatically everywhere."
}
\version "2.1.26"
\header { texidoc = "@cindex Bar line lyric only
-You can move around @code{Bar_engraver} and
-@code{Span_bar_engraver} if you want bar lines on lyrics. "
+You can move @code{Bar_engraver} and @code{Span_bar_engraver} to
+a different engraving context, if you want, for example, bar lines
+on lyrics. "
}
\score {
\version "2.1.26"
\header {
texidoc = "@cindex Bar Lines
-Different types of bar lines demonstrated.
+There a many types of bar lines available.
" }
% TODO: dashed "|", HJJ
\score
\header {
texidoc = "@cindex Bar Number Every Fifth Reset
If you would like the bar numbers to appear at regular intervals, but
-not starting from measure zero, you can use the context function,
-@code{set-bar-number-visibility}, to automatically set
-@code{barNumberVisibility} so that the bar numbers appear at regular
-intervals, starting from the @code{\applycontext}.
+not starting from measure zero, you can use a context function,
+@code{set-bar-number-visibility}, to set automatically
+@code{barNumberVisibility}, so that the bar numbers appear at regular
+intervals, starting from the measure in which
+@code{set-bar-number-visibility} is set using @code{\applycontext}.
"
}
\header {
texidoc = "
-Bar numbers can also be printed at regular intervals.
+Bar numbers can also be printed inside boxes.
" }
\version "2.1.26"
\header{
texidoc="@cindex Bar Number Show All
-Second line has bar numbers on start of every measure.
+By default, bar numbers are printed only in the first measure. This
+setting can be overridden, so that bar numbers on start of every measure.
" }
\score{
\header {
- texidoc = "Meshing eighths beams, connected by ties. This occurs
- in (for example) in the cello suites. See also
- @file{tie-cross-voice.ly}."
+ texidoc = "The eighth notes may be seemingly attached to different
+ beams, and the corresponding notes connected by ties (see also
+ @file{tie-cross-voice.ly}).
+ Such a situation may occur, for example, in the cello suites."
}
% keep for now, although merging into beam-auto-override is a possibility.
\header {
texidoc = "@cindex Auto Beaming 4/8
-You can override LilyPond's automatic beaming.
+You can override the automatic beaming settings.
"
}
texidoc = "@cindex Auto Beaming Override
-This shows how auto-beaming settings can be overridden.
-
-The auto-beamer will only engrave beams that end when:
+The auto-beamer, which can be overridden, will only engrave beams
+that end before encountering of
@itemize @bullet
-@item a rest is encountered
+@item a rest,
@item
- another beam (entered manually) is encountered
+ an other, manually entered beam, or
@item
- there's a 'gap' in the beam note's durations
+ a bar line.
@end itemize
-The beam will be ended also when now % beamAutoEnd = 0.
+The @code{autoBeaming} can also be turned off.
"
\version "2.1.26"
\header{
texidoc = "@cindex Beaming Presets
-The auto-beam engraver has presets for common time signatures. " }
+There are presets for the @code{auto-beam} engraver in the case of common
+time signatures. " }
\score{
\notes \relative c''{
\header{
texidoc="@cindex Beam Position Control
-Beam positions may be controlled manually, by setting @code{positions} in the @code{Beam} grob.
+Beam positions may be controlled manually, by overriding the @code{positions} setting of the @code{Beam} grob.
" }
\score {
\header{
texidoc="@cindex Beam Count
-You can alter the number of stems in a beam. Here we see
-two sets of four 32nds joined as if they were 8th notes.
+You can alter the number of stems in a beam. In this example,
+two sets of four 32nds are joined, as if they were 8th notes.
" }
#(override-auto-beam-setting '(end * * * *) 1 4)
f32 g a b b a g f
- f32 g a b
+ f32 g a
\set stemRightBeamCount = #1 b
- \set stemLeftBeamCount = #1 a
- g f
+ \set stemLeftBeamCount = #1 b
+ a g f
}
\header {
texidoc = "@cindex Beam Dir Functions
-There are several ways to calculate the direction of a beam:
+The direction of a beam may be calculated in several ways. As shown in
+the example, the beam are be below the notes if:
@table @code
@item majority
-number count of up or down notes
+of (individual) notes would have down stems,
@item mean
-mean center distance of all notes
+of note pitches is on the center line or below it, or
@item median
-mean centre distance weighted per note
+of note pithes (i.e. the centermost element of ordered pitches) is
+on the center line or below it.
@end table
-You can spot the differences of these settings from these simple
-examples:
-
-These beam direction functions are defined in @file{scm/beam.scm}. If
-your favourite algorithm isn't one of these, you can hook up your own.
+If your favourite algorithm is not one of these, you can hook up your
+own one.
+(These beam direction functions are defined in @file{scm/beam.scm}.)
"
}
\version "2.1.26"
\header{
texidoc="@cindex Beam Isknee
-LilyPond can beam across a Piano Staff.
+Beams can be placed across a \code{PianoStaff}.
" }
\score{
\context PianoStaff <<
\version "2.1.26"
\header{
texidoc="@cindex Beam Neutral Direction
-When a beam falls in the middle of the staff, LilyPond normally
-prints the beam pointing down. However, this behaviour can be
-altered if desired.
+When a beam falls in the middle of the staff, the beams point normally
+down. However, this behaviour can be altered, if desired.
" }
fragment = \notes {
\header{
texidoc="@cindex Beam Over Rests
-Beams over rests.
+Beams may be forced to be over rests.
" }
\score{
\header {
texidoc = "@cindex Invisible Notes
@cindex Blank Notes
-You can suppress printing of LilyPond output. This example shows you how to
-print invisible (or blank) notes. This can be very useful when you want to
-do wierd tricks with LilyPond (especially with slurs, since you can't attach
-a slur to a rest or spacer rest).
+Invisible (or transparent) can be useful, when wierd tricks are needed;
+especially, a slur cannot be attach to a rest or spacer rest.
" }
blanknotes = { \override NoteHead #'transparent = ##t
\header {
texidoc = "@cindex Blank Paper Tab
-Blank music paper, another example: empty staffs and a
-tablature staff. " }
+A blank music paper can be produced by using spacer rests, and removing
+@code{Bar_number_engraver}. Here is an empty staff with a tablature staff.
+" }
emptymusic = \notes { \repeat unfold 4 { s1\break } \bar "|." }
\header {
texidoc="@cindex Blank Paper
-Blank music paper with clefs. Change the repeat count to get more staves.
+A blank music paper can be produced also by using invisible notes, and removing
+@code{Bar_number_engraver}.
" }
\score {
\header {
texidoc = "@cindex Boxed Stencil
-You can override the print-function to draw a box around arbitrary grobs. " }
+The @code{print-function} can be overridden to draw a box around an arbitrary
+grob. " }
\score { \notes \relative c'' {
projects / lilypond.git / commitdiff