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.fly}
+@mudelafile{dots.ly}
Multiple measure rests do not collide with barlines and clefs. They
are not expanded when you set @code{Score.skipBars}. Although the
as half notes cannot appear in a regular beam, and should reach the
stems.
-@mudelafile{chord-tremolo.sly}
+@mudelafile{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.sly}
+@mudelafile{stem-direction.ly}
Similarly, if @code{stem_default_neutral_direction} is set to @code{-1}.
The staccato dot (and all scripts with follow-into-staff set), must
not be on staff lines.
-@mudelafile{staccato-pos.sly}
+@mudelafile{staccato-pos.ly}
+
+@section Chord names
+
+Chord names are generated from a list pitches, and are customisable
+from guile. For some unlogical names, guile customisation is used
+by default.
+
+@mudelafile{chord-names.ly}
@section Grace notes
second staff line. This does not hold for grace note beams.
Override with @code{noStemExtend}.
-@mudelafile{beam-position.sly}
+@mudelafile{beam-position.ly}
Slurs should look nice and symmetric. The curvature may increase
only to avoid noteheads, and as little as possible.
@mudelafile{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}
+
@section Repeats
LilyPond has three modes for repeats: folded, unfolded and
semi-unfolded. Unfolded repeats are fully written out. Semi unfolded
repeats have the body written and all alternatives sequentially.
Folded repeats have the body written and all alternatives
-simultaneously. If the number of alternatives is larger than the
+simultaneo.ly. If the number of alternatives is larger than the
repeat count, the excess alternatives are ignored. If the number of
alternatives is smaller, the first alternative is multiplied to get to
the number of repeats.
@mudelafile{repeat-fold.ly}
+Across linebreaks, the left edge of a first and second alternative
+bracket should be equal
+
+@mudelafile{repeat-line-break.ly}
+
+
+
@section Lyrics
Lyrics can be set to a melody automatically. Excess lyrics will be
adjusted. Barlines also are adjusted.
-@mudelafile{number-staff-lines.fly}
+@mudelafile{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.sly}
+@mudelafile{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
@mudelafile{clefs.ly}
+
+Key signatures appear on key changes. They may also
+appear without barlines. The restoration accidentals are not printed at
+the start of the line. If @code{createKeyOnClefChange} is set, they're
+also created on a clef change.
+
+@mudelafile{keys.ly}
+
@ignore
@c the input file is too long and does not test for specific bugs
+
By default, time signatures are written with two numbers. With style
``C'', 4/4 and 2/2 are written with their corresponding symbols and
with style ``old'', 2/2, 3/2, 2/4, 3/4, 4/4, 6/4, 9/4, 4/8, 6/8 and
layout. The style ``1'', gives single number signatures for all
signatures.
%
-\mu delafile{time.fly}
+\mu delafile{time.ly}
@end ignore
+
+
+@section Hacks and Features
+
+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}
+
@bye
+
projects / lilypond.git / blobdiff