it was designed.
+2004-02-19 Heikki Junes <hjunes@cc.hut.fi>
+
+ * input/regression/{many}.ly: refresh, trying to guess how
+ it was designed.
+
2004-02-18 Han-Wen Nienhuys <hanwen@xs4all.nl>
* VERSION: release 2.1.25
\header {
-texidoc = "Tied accidentaled notes (which cause reminder accidentals) don't wreak havoc in
-the spacing when unbroken."
+texidoc = "Tied accidentaled notes (which cause reminder accidentals) do not
+wreak havoc in the spacing when unbroken."
}
\version "2.1.25"
\version "2.1.22"
\header {
- texidoc = "A simple test for beams."
+ texidoc = "Beaming can be also given explicitly."
}
\paper { raggedright= ##t }
\header {
texidoc =
- "If @code{merge-differently-headed}, then
+ "If @code{merge-differently-headed} is enabled, then
open note heads may be merged with black noteheads, but only
if the black note heads are from 8th or shorter notes.
"
\version "2.1.22"
\header {
- texidoc = "If NoteCollision has merge-differently-dotted = \\#t note
+ texidoc = "If NoteCollision has merge-differently-dotted = ##t note
heads that have differing dot counts may be merged anyway. Dots
should not disappear when merging similar note heads."
Augmentation dots should never be printed on a staff line,
but rather be shifted vertically. They should go up, but in case of
multiple parts, the down stems have down shifted dots. In case of
-chords, all dots should be in a column. The dots go along as rests
-are shifted to avoid collisions.
+chords, all dots should be in a column. The dots follow the shift
+of rests when avoiding collisions.
-The priorities, are (ranked in importance):
+The priorities to print the dots are (ranked in importance):
@itemize @bullet
-@item keeping dots off staff lines
-@item keeping dots close to their note heads
-@item moving dots in the direction specified by the voice
-@item moving dots up
+@item keeping dots off staff lines,
+@item keeping dots close to their note heads,
+@item moving dots in the direction specified by the voice,
+@item moving dots up.
@end itemize
"
Figured bass is created by the FiguredBass context which eats
figured bass requests and rest-requests. You must enter these using
the special @code{\figures @{ @}} mode, which allows you to type
-numbers, like @code{<<4 6+>>}.
+numbers, like @code{<4 6+>}.
-You can also type letters by entering quoted strings, as demonstrated in the last example.
+You can also type letters by entering quoted strings.
" }
\score { \notes <<
\version "2.1.22"
\header{
- texidoc="Lyric phrasing
+ texidoc="
+ The multiple stanzas of lyric phrasing are aligned according to the start
+ and end of a phrase.
- The multiple stanzas are aligned according to the start and end of a phrase.
-
- Also, lyrics at the beginning of a melismata should be left aligned.
- (is that only lyrics that are followed by `__'? Because
- that seems to be the case now -- jcn)
+ By default, lyrics are centered with respect to the corresponding notes.
@example
- | | | | |
- x| x| x| x| x|
+ | | | | |
+ x| x| x| x| x|
1: Start sentence melisma end.
2: x x x______ x
@end example
- Only lyrics that are followed by '__' while there is a melisma,
+ While there is a melisma, lyrics are followed by '__' and they
are left-aligned, in this case the third x."
}
\header {
-texidoc= "Grace notes and multi-measure rests."
+texidoc= "Multi-measure rests are centered also in the case of grace notes."
}
\score {
\version "2.1.23"
-\header { texidoc = "This combines instrument names and multimeasure rests (there was an
-interesting bug in 1.3.98). " }
-
+\header { texidoc = "There are both long and short intstrument names.
+Engraving instrument names should not be confused by the
+multimeasure rests. " }
+% (there was an interesting bug in 1.3.98)
\score{
\context Staff <<
\set Staff.instrument = "instrument"
\header {
- texidoc = "By setting texts starting with a mmrest, an extra spacing
-column is created. This should not cause problems."
+ texidoc = "By setting texts starting with a multi-measure rest, an
+extra spacing column is created. This should not cause problems."
}
\version "2.1.22"
\header {
-texidoc = "With the new markup syntax, text may be written in various manenrs."
+texidoc = "With the new markup syntax, text may be written in various manners."
}
\version "2.1.22"
\version "2.1.22"
\header{
texidoc="
-Note head shapes are settable. The stem endings should be adjusted
-per note head. If you want different note head styles on one stem,
-you must create a special context called.
+Note head shapes may be set from several choices.
+The stem endings should be adjusted according to the note head.
+If you want different note head styles on one stem,
+you must create a special context.
Harmonic notes have a different shape and different
dimensions.
\header{
texidoc=" The number of stafflines of a staff can be set. Ledger
-lines both on note heads and rests are adjusted. Barlines also are
+lines both on note heads and rests, as well as barlines, are
adjusted accordingly. "
}
\header
{
-texidoc = "Ottava brackets behave properly at line breaks: there is
-no vertical line and the horizontal line does not stick out."
+texidoc = "At line breaks, ottava brackets have no vertical line and
+their horizontal line does not stick out."
}
texidoc = "Ottava brackets are supported, through the
use of the scheme function @code{set-octavation}.
-The spanner should go below for 8va bassa, and the string can be tuned
-with @code{Staff.ottavation}.
+The spanner should go below a staff for 8va bassa, and the ottavation
+string can be tuned with @code{Staff.ottavation}.
"
-\header { texidoc = "Solo/Solo2 also is global: In this example, solo1
- should not printed over the 1st note, because the voice
- switch would kill the slur."
+\header { texidoc = "In this example, solo1
+ should not be printed over the 1st note, because of the slur
+ which is present from the one-voice to the two-voice situation."
}
\header {
texidoc = "Distances between prefatory items (e.g. clef, bar, etc.)
- are done using engraving standard distances. These distances
+ are determined by engraving standards. These distances
depend on which items are combined."
}
\header { texidoc= "Rehearsal marks in letter style: the I is skipped,
-and after Z, we continue with double letters. The mark may be set
+and after Z, double letters are used. The mark may be set
with @code{\mark NUMBER}, or with @code{Score.rehearsalMark}."
}
\header { texidoc= "
Marks can be printed as numbers.
-By setting @code{markFormatter} we may choose a different style of mark printing. Also, marks can be specified manually, with a markup argument"
+By setting @code{markFormatter} we may choose a different style of mark printing. Also, marks can be specified manually, with a markup argument."
}
\header{
texidoc="
-Folded. This doesn't make sense without alternatives, but it works.
+Folded repeat may not make sense without alternatives, and there
+should not be more alternatives than repeats.
"
}
\header {
-texidoc = "Percent repeats are not skipped, even when skipBars is set. "
+texidoc = "Percent repeats are not skipped, even when @code{skipBars} is set."
}
\paper { raggedright= ##t }
\version "2.1.22"
\header {
-texidoc = "Measure repeats are supported, and may be nested with beat repeats."
+texidoc = "Measure repeats may be nested with beat repeats."
}
\score { \notes \relative c'' \context Voice { \time 4/4
\version "2.1.22"
\header {
-texidoc = "Beat repeats are supported."
+texidoc = "Within a bar, beat repeats denote that a music snippet should be
+played again."
}
\score { \notes \relative c'
texidoc = "In polyphonic situations, rests are moved down
even if there is no opposite note or rest. The amount is two
-staff-spaces. "
+@code{staff-space}s. "
}
\header{
texidoc="
-Rests. Note that the dot of 8th, 16th and 32nd rests rest should be
-next to the top of the rest. All rests except the whole rest are
-centered on the middle staff line.
+There is a big variety of rests. Note that the dot of 8th, 16th and 32nd
+rests rest should be next to the top of the rest. All rests except the
+whole rest are centered on the middle staff line.
"
}
\version "2.1.22"
\header{
texidoc="
-The same goes for slurs. They behave decently when broken across
-linebreak.
+Slurs behave decently when broken across a linebreak.
"
}
\version "2.1.22"
\header{
-texidoc="Slurs should not get confused by augmentation dots. We use a lot
-of dots here, to make problems more visible."
+texidoc="Slurs should not get confused by augmentation dots. With a lot
+of dots, the problems becomes more visible."
}
\score {
\notes\relative c'' {
\version "2.1.22"
\header {
-texidoc="Manual hack for slur and staccato."
+texidoc="An extra offset may be added between a slur and staccato(s)."
}
\paper { raggedright = ##t}
\version "2.1.22"
\header {
-texidoc = "Accidentals in different staves don't effect the
+texidoc = "Accidentals in different staves do not affect the
spacing of the quarter notes here."
}
\version "2.1.25"
\header {
- texidoc = "Accidentals don't influence the amount of stretchable space. "
+ texidoc = "Accidentals do not influence the amount of stretchable space. "
}
\score {
\version "2.1.22"
\header {
- texidoc ="Broken matter at the end of line does not upset the
- space following rests and notes." }
+ texidoc ="Broken engraving of a bar at the end of a line does not upset
+ the space following rests and notes." }
\score
{
\version "2.1.22"
\header {
texidoc = "A clef can be folded below notes in a different staff, if
-this doesn't disrupt the flow of the notes."
+this does not disrupt the flow of the notes."
}
\score { \notes \relative c'' <<
\version "2.1.22"
\header {
- texidoc = "Grace note spacing. Should be tuned? "
+ texidoc = "Grace note spacing. Should it be tuned? "
}
\score {
\version "2.1.22"
\header{
-texidoc = "Concurrent tuplets should be spaced equidistantly on
-all staffs.
+texidoc = "Concurrent tuplets should be equidistant on all staffs.
-Note that this only spaces correctly (exactly) when raggedright
-is. For non-raggedright, it still shows a bug: uneven spacing.
+Note that this only spaces correctly (exactly) when @code{raggedright}
+is enabled. For a non-@code{raggedright} case, it still shows a bug:
+uneven spacing.
" }
\version "2.1.22"
\header {
texidoc = "Rests get a little less space, since they are narrower.
-However, the feta quarter rest is relatively wide, causing this effect to be
-very small.
+However, the quarter rest in feta font is relatively wide, causing this
+effect to be very small.
"
}
\score { \notes \relative c'' \context Staff {
\version "2.1.22"
\header {
-texidoc = "Notes that are shorter than the common shortest note, Get a
+texidoc = "Notes that are shorter than the common shortest note get a
space (i.e. without the space needed for the note) proportional to
-their duration. So 16th notes get 1/2 of the space of an eigth note.
-The total distance for a 16th is (including note head) is 3/4 of the
+their duration. So, the 16th notes get 1/2 of the space of an eigth note.
+The total distance for a 16th (which includes note head) is 3/4 of the
eighth note. "
}
texidoc="
-LilyPond corrects for optical spacing of stems. The overlap between to
-adjacent stems of different direction is used as a measure for how
+There are optical corrections to the spacing of stems. The overlap between
+two adjacent stems of different direction is used as a measure for how
much to correct."
}
\version "2.1.22"
\header {
texidoc = "For juxtaposed chords with the same direction, a
-slight optical correction is used. It is constant, and only works if
+slight optical correction is used. It is constant, and works only if
two chords have no common head-positions range."
}
\version "2.1.22"
\header {
- texidoc ="Space from a normal note/barline to a grace note is
+ texidoc ="Space from a normal note (or barline) to a grace note is
smaller than to a normal note."
}
\version "2.1.22"
\header {
texidoc = "
- When tightly spaced, hinterfleisch -> 0.
- Stems may touch the bar lines, opposite stems may touch eachother.
- We need a mininum of about a note-width/interline space in these
- situations, so that in tightly spaced music all vertical lines
- are about equally spaced.
+ When tightly spaced, the spaces between elements (hinterfleisch?)
+ may approach zero. In that case,
+ stems may touch the bar lines and opposite stems may touch eachother.
+ In these situations,
+ a mininum of about a note-width/interline space is needed,
+ so that all vertical lines are approximately equally spaced in tightly
+ spaced music.
"
\version "2.1.23"
\header {
-texidoc = "Span bars draw only in between staff bar lines, so setting those to transparent shows bar lines between systems only.
+texidoc = "Span bars are drawn only between staff bar lines. By setting
+bar lines to transparent, they are shown only between systems.
"
}
\header{
texidoc="
-The staccato dot (and all scripts with follow-into-staff set), must
+The staccato dot (and all scripts with follow-into-staff set) must
not be on staff lines.
"
}
\header {
texidoc = "Staves may be present in several sizes within a score.
-This is achieved with an internal scaling factor. When code forgets to
-take into account the scaling factor, objects generally become too
-thick or too large on smaller staves."
+This is achieved with an internal scaling factor. If the scaling factor is
+forgotten in some places, objects generally become too thick or too
+large on smaller staves."
}
\version "2.1.22"
\header {
-texidoc = "The staff is a grob, and may be adjusted as well: this one
- shows a staff with 6 thick line, and a slightly large staffspace.
-Beams remain correctly quantized."
+texidoc = "The staff is a grob (graphical object) which may be adjusted as well, for example, to have 6 thick lines and a slightly large @code{staff-space}.
+However, beams remain correctly quantized."
}
\header{
texidoc="
-In a limited number of cases, LilyPond corrects for optical spacing
-effects. In this example, space for opposite pointed stems is adjusted.
+In a limited number of cases, the optical spacing effects are corrected.
+In this example, space for opposite pointed stems is adjusted.
"
}
\version "2.1.23"
\header {
- texidoc = "LilyPond correctly determines the size of every
- system. This includes postscript constructs such as slurs."
+ texidoc = "The size of every system is correctly determined; this
+ includes postscript constructs such as slurs."
}
accidental must not be drawn on the note in the next bar. Unless the
tie crosses a line break, in which case the accidental is repeated if
it would be different from an untied note. The next note of the same
-pitch in this next bar should always show the accidental (even if it's
+pitch in this next bar should always show the accidental (even if it is
natural). Slurring a accidentaled note to a natural one across bar
boundaries should be explicit.
\header {
texidoc = "First and second bes (tied across line break)
should get an accidental, but others should not.
-Only first B should get natural sign."
+Only first b should get natural sign."
}
\score {
\header {
texidoc = "Tie engraver uses @code{busyGrobs} to keep track of
-note heads. Test if this queue works by throwing many mixed tuplets at it.
-
-This test may show collisions between tie and beam.
+note heads. By throwing many mixed tuplets on the queue,
+one may have collisions between ties and beams.
"
}
\header{
texidoc="
When tying chords, the outer slurs point outwards, the inner slurs
-point away from the center of the staff. Override with
-@code{tieVerticalDirection}.
+point away from the center of the staff. The behavior can be overridden
+by setting explicitly the @code{direction} of a @code{TieColumn}.
"
}
\version "2.1.25"
\header {
- texidoc="Manual hack for nested tuplets, move outer tuplet up."
+ texidoc="By a manual hack for nested tuplets, an outer tuplet can be moved up."
}
#(define (make-text-checker-once text)
\header {
-texidoc = "Tuplet bracket formatting supports numerous options:
-NB should have no bracket, B should have bracket.
+texidoc = "Tuplet bracket formatting supports numerous options,
+for instance, bracketed (B) and non-bracketed (NB).
"
}
\version "2.1.22"
\header {
-texidoc ="Broken volta spanners behave correctly at left edge in all cases."
+texidoc ="Broken volta spanners behave correctly at their left edge in all cases."
}
projects / lilypond.git / commitdiff