@title LilyPond Regression test
@end ignore
-@node Top, , ,
+@node Top, , , (dir)
@section Introduction
-This document tries give an brief overview of LilyPond features. When
+This document tries give a brief overview of LilyPond features. When
the text correspond with the shown notation, we consider LilyPond
Officially BugFree (tm). This document is intended for finding bugs,
and documenting bugfixes.
+[TODO: revise and completize this. ]
+
+[TODO: should generate out of header fields using ly2dvi?]
+
+
+
@section Notes and rests
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.
-@mudelafile{rest.ly}
+@lilypondfile{rest.ly}
Note head shapes are settable. The stem endings should be adjusted
per note head. If you want different note head styles on one stem,
dimensions. Nevertheless, noteheads in both styles can be combined, on
either up or down stems.
-@mudelafile{noteheadstyle.ly}
+@lilypondfile{noteheadstyle.ly}
Noteheads can have dots, and rests can too. Augmentation dots should
never be printed on a staff line, but rather be shifted vertically. They
shifted dots. (Wanske p. 186) In case of chords, all dots should be in
a column. The dots go along as rests are shifted to avoid collisions.
-@mudelafile{dots.ly}
+@lilypondfile{dots.ly}
+
+Accidentals work: the second note does not get a sharp. The third and
+fourth show forced and courtesy accidentals
+
+@lilypondfile{accidental.ly}
Multiple measure rests do not collide with barlines and clefs. They
are not expanded when you set @code{Score.skipBars}. Although the
multi-measure-rest is a Spanner, minimum distances are set to keep it
colliding from barlines.
-@mudelafile{multi-measure-rest.ly}
+
+@lilypondfile{multi-measure-rest.ly}
If @code{Score.skipBars} is set,
the signs for four, two, and one measure rest are combined to
produce the graphical representation of rests for up to 10 bars.
The number of bars will be written above the sign.
-@mudelafile{mm-rests2.ly}
+@lilypondfile{mm-rests2.ly}
A sharp sign after a double sharp sign, as well as a flat sign
after a double flat sign is automatically prepended with a
natural sign.
-@mudelafile{double-single-acc.ly}
+@lilypondfile{accidental-single-double.ly}
@section Stems
to the beam. If the stem is invisible (eg. on a whole note), the
tremolo must be centered on the note.
-@mudelafile{stem-tremolo.ly}
+@lilypondfile{stem-tremolo.ly}
Chord tremolos look like beams, but are a kind of repeat symbol.
To avoid confusion, chord tremolo beams do not reach the stems, but
as half notes cannot appear in a regular beam, and should reach the
stems.
-@mudelafile{chord-tremolo.ly}
+@lilypondfile{chord-tremolo.ly}
Beams, stems and noteheads often have communication troubles, since
the two systems for y dimensions (1 unit = staffspace, 1 unit = 1
on the middle staff line. Of course stem-direction is down for high
notes, and up for low notes.
-@mudelafile{stem-direction.ly}
+@lilypondfile{stem-direction.ly}
Similarly, if @code{stem_default_neutral_direction} is set to @code{-1}.
-@mudelafile{stem-direction-down.ly}
+@lilypondfile{stem-direction-down.ly}
@section Scripts
The staccato dot (and all scripts with follow-into-staff set), must
not be on staff lines.
-@mudelafile{staccato-pos.ly}
+@lilypondfile{staccato-pos.ly}
+
+Dynamics appear below or above the staff. If multiple dynamics are
+linked with (de)crescendi, they should be on the same line.
+
+@lilypondfile{dyn-line.ly}
+
+
+Arpeggios are supported, both cross-staff and one-staff.
+
+@lilypondfile{arpeggio.ly}
+
+
@section Chord names
from guile. For some unlogical names, guile customisation is used
by default.
-@mudelafile{chord-names.ly}
+@lilypondfile{chord-names.ly}
@section Grace notes
Grace notes without beams should have a slash, if @code{flagStyle} is
not set. Main note scripts don't end up on the grace note.
-@mudelafile{grace.ly}
-
+@c @lily pondfile{grace.ly}
@section Beams, slurs and other spanners
case, line breaks are forbidden. Yet clef and key signatures are
hidden just as with breakable bar lines.
-@mudelafile{beaming.ly}
+@lilypondfile{beaming.ly}
Beams should behave reasonably well, even under extreme circumstances.
Stems may be short, but noteheads should never touch the beam.
-@mudelafile{beam-extreme.ly}
+@lilypondfile{beam-extreme.ly}
Beams should always reach the middle staff line. The second beam
counting from the note head side, should never be lower than the
second staff line. This does not hold for grace note beams.
Override with @code{noStemExtend}.
-@mudelafile{beam-position.ly}
+@c @lily pondfile{beam-position.ly}
Slurs should look nice and symmetric. The curvature may increase
-only to avoid noteheads, and as little as possible.
+only to avoid noteheads, and as little as possible. Slurs never
+run through noteheads or stems.
+
+@lilypondfile{slur-nice.ly}
+@lilypondfile{slur-symmetry.ly}
+@lilypondfile{slur-symmetry-1.ly}
-@mudelafile{slur-symmetry.ly}
-@mudelafile{slur-symmetry-1.ly}
+Across line breaks, slurs behave nicely. On the left, they extend to
+just after the preferatory matter, and on the right to the end of the
+staff. A slur should follow the same vertical direction it would have
+in unbroken state.
+
+@lilypondfile{slur-broken-trend.ly}
Ties are strictly horizontal. They are placed in between note heads.
The horizontal middle should not overlap with a staffline.
-@mudelafile{tie.ly}
+@lilypondfile{tie.ly}
When tieing chords, the outer slurs point outwards, the inner slurs
point away from the center of the staff. Override with
@code{tieVerticalDirection}.
-@mudelafile{tie-chord.ly}
+@lilypondfile{tie-chord.ly}
When tieing notes with accidentals across a bar boundary, the accidental
must not be drawn on the note in the new bar. Instead, the next note of
Pitches can be verified by printing them with the @code{NoteNames} context.
-@mudelafile{tie-accidental.ly}
+@lilypondfile{tie-accidental.ly}
Beams can be typeset over fixed distance aligned staffs, beam
beautification doesn't really work, but knees do. Beams should be
behave well, wherever the switching point is.
-@mudelafile{beam-cross-staff.ly}
+@lilypondfile{beam-cross-staff.ly}
The same goes for slurs. They behave decently when broken across
linebreak.
-@mudelafile{slur-cross-staff.ly}
+@lilypondfile{slur-cross-staff.ly}
Tuplets are indicated by a bracket with a number. There should be no
bracket if there is one beam that matches the length of the tuplet.
The bracket does not interfere with the stafflines, and the number is
centered in the gap in the bracket.
-@mudelafile{tup.ly}
+@lilypondfile{tup.ly}
@section Property details
More specific settings take precendence over less specific settings. The
second slur has slurDirection set to down, overriding the stemup setting.
-@mudelafile{generic-property-override.ly}
+@lilypondfile{generic-property-override.ly}
@section Repeats
Unfolded behavior:
-@mudelafile{repeat-unfold.ly}
+@lilypondfile{repeat-unfold.ly}
Volta (Semi folded) behavior. Voltas can start on non-barline moments.
If they don't barlines should still be shown.
-@mudelafile{repeat-volta.ly}
+@lilypondfile{repeat-volta.ly}
Folded. This doesn't make sense without alternatives, but it works.
-@mudelafile{repeat-fold.ly}
+@lilypondfile{repeat-fold.ly}
Across linebreaks, the left edge of a first and second alternative
bracket should be equal
-@mudelafile{repeat-line-break.ly}
+@lilypondfile{repeat-line-break.ly}
+Auto change piano staff switches voices between up and down staffs
+automatically; rests are switched along with the coming note.
+@lilypondfile{auto-change.ly}
@section Lyrics
extenders do not assume anything about lyric lengths, so they continue
to work.
-@mudelafile{lyric-combine.ly}
+@lilypondfile{lyric-combine.ly}
+
+Multiple stanzas
+
+@lilypondfile{lyrics-multi-stanza.ly}
@section Multiple notes
and whole rests just outside the staff get ledger lines in different
cases.
-@mudelafile{rest-collision.ly}
+@lilypondfile{rest-collision.ly}
Normal collisions. We have support for polyphony, where the
middle voices are horizontally shifted.
-@mudelafile{collisions.ly}
+@lilypondfile{collisions.ly}
The number of stafflines of a staff can be set with the property
numberOfStaffLines. Ledger lines both on note heads and rests are
adjusted. Barlines also are adjusted.
-@mudelafile{number-staff-lines.ly}
+@lilypondfile{number-staff-lines.ly}
@section Spacing
In a limited number of cases, LilyPond corrects for optical spacing
effects. In this example, space for opposite pointed stems is adjusted
-@mudelafile{stem-spacing.ly}
+@lilypondfile{stem-spacing.ly}
If there are accidentals in the music, we add space, but the space
between note and accidentals is less than between the notes with the
same value. Clef changes also get extra space, but not as much as
barlines.
-
Even if a line is very tightly spaced, there will still be room
between prefatory matter and the following notes. The space after the
prefatory is very rigid. In contrast, the space before the barline
Tight:
-@mudelafile{spacing-tight.ly}
+@lilypondfile{spacing-tight.ly}
Natural:
-@mudelafile{spacing-natural.ly}
+@lilypondfile{spacing-natural.ly}
Loose:
-@mudelafile{spacing-loose.ly}
+@lilypondfile{spacing-loose.ly}
Adding a @code{Bar_engraver} to the LyricsVoice context makes sure that
lyrics don't collide with barlines.
-@mudelafile{lyrics-bar.ly}
+@lilypondfile{lyrics-bar.ly}
+
+Text is set with empty horizontal dimensions. The boolean property
+textNonEmpty is used to respect the horizontal size of text.
+
+@lilypondfile{non-empty-text.ly}
+
+
+
+
+@section PianoStaff
+
+
@section Global stuff
Breaks can be encouraged and discouraged using @code{\break} and
@code{\nobreak}. They are abbrevs for @code{\penalty} commands.
-@mudelafile{break.ly}
-
+@lilypondfile{break.ly}
Markings that are attached to (invisible) barlines are
delicate: the are attached to the rest of the score without the score
knowing it. Consequently, they fall over often.
-@mudelafile{bar-scripts.ly}
+@lilypondfile{bar-scripts.ly}
Staff margins are also markings attached to barlines. They should be
left of the staff, and be centered vertically wrt the staff. They may
be on normal staffs, but also on compound staffs, like the PianoStaff
-@mudelafile{staff-margin.ly}
+@lilypondfile{staff-margin.ly}
Breathing signs, also used for phrasing, do normally not influence
global spacing -- only if space gets tight, notes are shifted to make
through their voice. In the following example, the notes in the first
two measures all have the same distance from each other:
-@mudelafile{breathing-sign.ly}
+@lilypondfile{breathing-sign.ly}
Hara kiri staffs kill themselves if they are empty. This example really
contains two staffs, but the second contains only spaces, and is
therefore removed.
-@mudelafile{hara-kiri-short.ly}
+@lilypondfile{hara-kiri-short.ly}
+
+In orchestral scores and hymns, voices are traditionally combined onto
+one staff. LilyPond has a part combiner, that combines or separates two
+voices according to actual rhythm and pitch. User-defined texts such as
+``solo'' and ``@`a2'' are typeset automagically, as appropriate.
+
+@lilypondfile{part-combine.ly}
Fonts are available in a default set of sizes: 11, 13, 16, 20, 23 and
26pt staffheight. Sizes of the text fonts and symbol fonts are made
to match the staff dimensions.
-@mudelafile[nofly]{size11.ly}
+@lilypondfile[nonfragment]{size11.ly}
-@mudelafile[nofly]{size13.ly}
+@lilypondfile[nonfragment]{size13.ly}
-@mudelafile[nofly]{size16.ly}
+@lilypondfile[nonfragment]{size16.ly}
-@mudelafile[nofly]{size20.ly}
+@lilypondfile[nonfragment]{size20.ly}
-@mudelafile[nofly]{size23.ly}
+@lilypondfile[nonfragment]{size23.ly}
-@mudelafile[nofly]{size26.ly}
+@lilypondfile[nonfragment]{size26.ly}
@section Clefs and Time Signatures
below the clef respectively. The ``8'' is processed in a convoluted
way, so this is fragile as well.
-@mudelafile{clefs.ly}
+@lilypondfile{clefs.ly}
Key signatures appear on key changes. They may also
the start of the line. If @code{createKeyOnClefChange} is set, they're
also created on a clef change.
-@mudelafile{keys.ly}
+@lilypondfile{keys.ly}
+
+
+
@ignore
@c the input file is too long and does not test for specific bugs
As a last resort, the placement of items can be adjusted manually, by
setting the @code{extra-offset} of an output object.
-@mudelafile{generic-output-property.ly}
+@lilypondfile{generic-output-property.ly}
+
+The same mechanism can be used to force pagebreaks.
+
+@lilypondfile{between-systems.ly}
@bye
projects / lilypond.git / blobdiff