Notation Reference: see @ref{Clef}.
-@refbugs
+@knownissues
The mensural g clef is mapped to the Petrucci g clef.
music, the default flag style should be used. There are no flags in
Gregorian Chant notation.
-@refbugs
+@knownissues
The attachment of ancient flags to stems is slightly off due to a
change in early 2.3.x.
This manual: @ref{Time signature}, gives a general introduction to
the use of time signatures.
-@refbugs
+@knownissues
Ratios of note durations do not change with the time signature. For
example, the ratio of 1 brevis = 3 semibrevis (tempus perfectum) must
}
@end lilypond
-@refbugs
+@knownissues
Some articulations are vertically placed too closely to the
corresponding note heads.
@lilypondfile[quote,ragged-right]{divisiones.ly}
-@refcommands
+@predefined
@funindex \virgula
@code{\virgula},
-@refbugs
+@knownissues
Ligatures need special spacing that has not yet been implemented. As
a result, there is too much space between ligatures most of the time,
}
@end lilypond
-@refbugs
+@knownissues
Horizontal spacing is poor.
}
@end lilypond
-@refcommands
+@predefined
The following head prefixes are supported
@funindex \augmentum
Use the unary music function @code{\augmentum} to add augmentum dots.
-@refbugs
+@knownissues
When an @code{\augmentum} dot appears at the end of the last staff
within a ligature, it is sometimes vertically placed wrong. As a
@end lilypond
-@commonprop
+@snippets
By default, this method produces figures above the notes. To get
figures below the notes, use
@end example
-@refbugs
+@knownissues
When using figured bass above the staff with extender lines and
@code{implicitBassFigures} the lines may become swapped around.
@internalsref{All layout objects}.
-@refbugs
+@knownissues
The back-end is not very strict in type-checking object properties.
Cyclic references in Scheme values for properties can cause hangs
-@refbugs
+@knownissues
It is not possible to collect context changes in a variable and apply
them to a @code{\context} definition by referring to that variable.
-@refbugs
+@knownissues
Each step can only be present in a chord once. The following
simply produces the augmented chord, since @code{5+} is interpreted
@cindex chords, jazz
-@refcommands
+@predefined
@funindex \germanChords
@code{\germanChords},
@file{scm/@/chord@/-entry@/.scm}.
-@refbugs
+@knownissues
Chord names are determined solely from the list of pitches. Chord
inversions are not identified, and neither are added bass notes. This
on the command-line; see @ref{Command-line usage} for more information.
-@refbugs
+@knownissues
We unfortunately do not have the resources to maintain these
programs; please consider them @qq{as-is}. Patches are appreciated, but
bug reports will almost certainly not be resolved.
@end table
-@refbugs
+@knownissues
Overlapping notes in an arpeggio will not be correctly rendered. The
first note will be read and the others will be ignored. Set them all
into the current line of lyrics.
-@refbugs
+@knownissues
The ABC standard is not very @q{standard}. For extended features
(e.g., polyphonic music) different conventions exist.
@end table
-@refbugs
+@knownissues
The list of articulation scripts is incomplete. Empty measures
confuse @command{etf2ly}. Sequences of grace notes are ended improperly.
use fonts. These are the ones supporting the @code{font-interface}
layout interface.
-@refcommands
+@predefined
The following commands set @code{fontSize} for the current voice:
@end lilypond
-@commonprop
+@snippets
@code{fingeringOrientations} are used to control where the fingering
numbers are placed.
c
@end lilypond
-@refcommands
+@predefined
@code{\hideNotes}, @code{\unHideNotes}
Snippets: @lsrdir{Editorial,Editorial-annotations}.
-@refbugs
+@knownissues
Not all x11 colors are distinguishable in a web browser i.e. a web
browser might not display a difference between 'LimeGreen and
'ForestGreen. For web use normal colors are recommended. (#blue,
automatically. For whole notes and rests, they are also created but
made invisible.
-@refcommands
+@predefined
@funindex \stemUp
@code{\stemUp},
@code{\stemNeutral}.
-@commonprop
+@snippets
@cindex stem, direction
@cindex stem, up
@cindex varcoda
-@commonprop
+@snippets
The shorthands are defined in @file{ly/@/script@/-init@/.ly},
where the variables @code{dashHat}, @code{dashPlus},
@internalsref{TextScript}.
-@refbugs
+@knownissues
These signs appear in the printed output but have no effect on the
MIDI rendering of the music.
@internalsref{DynamicLineSpanner}.
-@refcommands
+@predefined
@funindex \dynamicUp
@code{\dynamicUp},
@code{\dynamicNeutral}.
-@commonprop
+@snippets
Dynamics that occur at, begin on, or end on the same note will be
vertically aligned. If you want to ensure that dynamics are
slur over a few small slurs, please see @ref{Phrasing slurs}.
-@refcommands
+@predefined
@funindex \slurUp
@code{\slurUp},
@code{\slurSolid}.
-@commonprop
+@snippets
Some composers write two slurs when they want legato chords. This
can be achieved in LilyPond by setting @code{doubleSlurs},
You cannot have simultaneous phrasing slurs.
-@refcommands
+@predefined
@funindex \phrasingSlurUp
@code{\phrasingSlurUp},
@end lilypond
-@commonprop
+@snippets
The glyph of the breath mark can be tuned by overriding the
@code{text} property of the @code{BreathingSign} layout object
c2\glissando c,
@end lilypond
-@commonprop
+@snippets
@lilypond[verbatim,quote,ragged-right]
Internals Reference: @internalsref{Glissando}.
-@refbugs
+@knownissues
Printing text over the line (such as @emph{gliss.}) is not
supported.
@end lilypond
-@refcommands
+@predefined
@code{\arpeggio},
@funindex \arpeggioUp
@code{\arpeggioBracket}.
-@commonprop
+@snippets
In a @code{PianoStaff}, it is possible to let an arpeggio cross
between the staves by setting the property
@internalsref{PianoStaff}.
-@refbugs
+@knownissues
It is not possible to mix connected arpeggios and unconnected
arpeggios in one @code{PianoStaff} at the same point in
printed as a stemless note head in parentheses.
-@refcommands
+@predefined
@code{\startTrillSpan},
@funindex \startTrillSpan
@end lilypond
-@commonprop
+@snippets
To print tablatures with stems down and horizontal beams,
initialize the @code{TabStaff} with this code:
Internals Reference: @internalsref{TabNoteHead}, @internalsref{TabStaff}, @internalsref{TabVoice}.
-@refbugs
+@knownissues
Chords are not handled in a special way, and hence the automatic
string selector may easily select the same string to two notes in a
tunings.
Internals Reference: @internalsref{Tab_note_heads_engraver}.
-@refbugs
+@knownissues
No guitar special effects have been implemented.
@cindex fingerings, right hand, for guitar
@cindex right hand fingerings for guitar
-@commonprop
+@snippets
You may exercise greater control over right handing fingerings by
setting @code{strokeFingerOrientations},
Examples: @c @lsr{parts,tag@/-filter@/.ly}
-@refbugs
+@knownissues
Multiple rests are not merged if you create the score with both tagged
sections.
You may build the manual ( Documentation/user/ ) without building all
the input/* stuff.
-@refbugs
+@knownissues
You may also need to create a script for @command{pngtopnm} and
@code{pnmtopng}. On Linux, I use this:
@end ignore
-@commonprop
+@snippets
Sometimes it is useful to display music elements (such as ties and slurs)
as if they continued after the end of the fragment. This can be done by
Print version information.
@end table
-@refbugs
+@knownissues
The Texinfo command @code{@@pagesizes} is not interpreted. Similarly,
@LaTeX{} commands that change margins and line widths after the preamble
@c **** Headings in a doc subsection ****
-@c obsolete; being removed.
-@macro refcommands
+@macro predefined
@noindent
@subsubheading Predefined commands
@end macro
-@macro commonprop
+@macro snippets
@noindent
-@c @subsubheading Commonly tweaked properties
@subsubheading Selected Snippets
@end macro
@indent
@end macro
-@macro refbugs
+@macro knownissues
@noindent
@subsubheading Known issues and warnings
@end macro
-
@macro funindex {TEXT}
@findex \TEXT\
@kindex \TEXT\
@c **** Links and references ****
-@c usage: @lsr{ancient,Ancient-notation,custodes.ly}
-@ignore
-
-DEPRECATED
-
-@macro lsr{SECTION,DIR,TEXT}
-@ifhtml
-@uref{source/input/lsr/snippets/\DIR\.html#\TEXT\,@file{\SECTION\/\TEXT\}}
-@end ifhtml
-@ifnothtml
-@file{\SECTION\/\TEXT\}
-@end ifnothtml
-@end macro
-@end ignore
-
@c usage: @lsrdir{ancient,Ancient-notation}
@macro lsrdir{SECTION,DIR}
@ifhtml
dimensions. If the book has between 10 and 99 pages, it may be "00",
ie. a two digit number.
-@refcommands
+@predefined
@funindex \label
@code{\label}
Init files: @file{ly/@/toc@/-init@/.ly}.
-@refcommands
+@predefined
@funindex \table-of-contents
@code{\table-of-contents}
that are off or accidentals that were mistyped stand out very much
when listening to the MIDI output.
-@refbugs
+@knownissues
Many musically interesting effects, such as swing, articulation,
slurring, etc., are not translated to midi.
@end example
-@refbugs
+@knownissues
Unterminated (de)crescendos will not render properly in the midi file,
resulting in silent passages of music. The workaround is to explicitly
Internals Reference: @internalsref{DrumStaff}, @internalsref{DrumVoice}.
-@refbugs
+@knownissues
Because general MIDI does not contain rim shots, the sidestick is used
for this purpose instead.
* Cross staff stems::
@end menu
-@refbugs
+@knownissues
Dynamics are not centered, but workarounds do exist. See the
@q{piano centered dynamics} template in @rlearning{Piano templates}.
-@refbugs
+@knownissues
The staff switches may not end up in optimal places. For high
quality output, staff switches should be specified manually.
Internals Reference: @internalsref{VoiceFollower}.
-@refcommands
+@predefined
@funindex \showStaffSwitch
@code{\showStaffSwitch},
@funindex \chordmode
@funindex \relative
-@refbugs
+@knownissues
The relative conversion will not affect @code{\transpose},
@code{\chordmode} or @code{\relative} sections in its argument.
@end lilypond
-@commonprop
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
{preventing-extra-naturals-from-being-automatically-added.ly}
Snippets: @lsrdir{Pitches,Pitches}.
-@refbugs
+@knownissues
There are no generally accepted standards for denoting
quarter-tone accidentals, so LilyPond's symbol does not conform to
see @ref{Instrument transpositions}.
-@commonprop
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
{transposing-pitches-with-minimum-accidentals-smart-transpose.ly}
@funindex \chordmode
@funindex \relative
-@refbugs
+@knownissues
The relative conversion will not affect @code{\transpose},
@end lilypond
-@commonprop
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
{clefs-commonly-tweaked-properties.ly}
@end lilypond
-@commonprop
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
{preventing-natural-signs-from-being-printed-when-the-key-signature-changes.ly}
2@tie{}(for 15ma), and -2 (for 15ma bassa) as arguments.
-@commonprop
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
{ottava-text.ly}
@end lilypond
@end table
-@commonprop
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
{dodecaphonic-style-accidentals-for-each-note-including-naturals.ly}
@cindex accidentals in chords
@cindex chords, accidentals in
-@refbugs
+@knownissues
Simultaneous notes are considered to be entered in sequential
mode. This means that in a chord the accidentals are typeset as
@cindex range of pitches
@cindex pitch range
-@c FIXME: square brackets for plural ?
The term @notation{ambitus} (pl. ambitus) denotes a range of
pitches for a given voice in a part of music. It may also denote
the pitch range that a musical instrument is capable of playing.
@end lilypond
-@commonprop
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
{adding-ambiti-per-voice.ly}
@internalsref{Staff}, @internalsref{Voice}.
-@refbugs
+@knownissues
There is no collision handling in the case of multiple per-voice
ambitus.
in a large font size. To print with a larger font, see @ref{Setting the
staff size}.
-@refcommands
+@predefined
@funindex \easyHeadsOn
@funindex \easyHeadsOff
Shapes are typeset according to the step in the scale, where
the base of the scale is determined by the @code{\key} command.
-@commonprop
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
{applying-noteheads-styles-depending-on-the-step-of-the-scale.ly}
@end lilypond
-@refcommands
+@predefined
@funindex \improvisationOn
@funindex \improvisationOff
The order of headings inside documentation sections should be:
main docs
-@refcommands
-@commonprop
+@predefined
+@snippets
@seealso
-@refbugs
+@knownissues
* You _must_ include a @seealso. The order of items inside the
@seealso section is
@end example
-@refbugs
+@knownissues
Mixing Scheme and LilyPond variables is not possible with the
@code{--safe} option.
@ref{New markup command definition}).
-@refbugs
+@knownissues
The markup-list argument of commands such as @code{#:line},
@code{#:center}, and @code{#:column} cannot be a variable or
@c Examples:
-@refbugs
+@knownissues
@cindex repeat, ambiguous
@end lilypond
-@refbugs
+@knownissues
Tremolos entered with @q{@code{:}[@var{number}]} do not carry over
duration. For details of this and other settings which control
proportional notation, see @ref{Proportional notation}.
-@refcommands
+@predefined
Dots are normally moved up to avoid staff lines, except in
polyphonic situations. The following commands may be used to
@internalsref{DotColumn}.
-@refbugs
+@knownissues
@c Deliberately duplicated in Durations and Rests. -gp
There is no fundamental limit to rest durations (both in terms of
}
@end lilypond
-@refcommands
+@predefined
@funindex \tupletUp
@code{\tupletUp},
@code{\tupletNeutral}.
-@commonprop
+@snippets
@cindex tuplet formatting
@cindex triplet formatting
Internals Reference: @internalsref{TupletBracket},
@internalsref{TupletNumber}, @internalsref{TimeScaledMusic}.
-@refbugs
+@knownissues
Lines may be broken within a tuplet with @code{\bar "" \break},
but the tuplet bracket does not correctly carry over.
@end lilypond
@end quotation
-@refcommands
+@predefined
@funindex \tieUp
@code{\tieUp},
@code{\tieSolid}.
-@commonprop
+@snippets
Ties are sometimes used to write out arpeggios. In this case, two
tied notes need not be consecutive. This can be achieved by
Internals Reference: @internalsref{Tie}.
-@refbugs
+@knownissues
Switching staves when a tie is active will not produce a slanted
tie.
Internals Reference: @internalsref{Rest}.
-@refbugs
+@knownissues
@c Deliberately duplicated in Durations and Rests. -gp
There is no fundamental limit to rest durations (both in terms of
specified texts.
-@refbugs
+@knownissues
If an attempt is made to use fingerings (e.g.,
@code{R1*10-4}) to put numbers over multi-measure rests, the
\time 2/4 c2 \time 3/4 c2.
@end lilypond
-@commonprop
+@snippets
The symbol that is printed can be customized with the @code{style}
property. Setting it to @code{#'()} uses fraction style for 4/4
Examples: @c @lsr{contemporary,compound-time-signature.ly}.
-@refbugs
+@knownissues
Automatic beaming does not use the measure grouping specified with
@code{set-time-signature}.
translated to mean @qq{there is a quarter note left in the bar.}
-@refbugs
+@knownissues
This command does not take into account grace notes at the start
of the music. When a piece starts with grace notes in the
d4 e d c
@end lilypond
-@refbugs
+@knownissues
LilyPond will only insert line breaks and page breaks at a
bar line. Unless the unmetered music ends before the end of the
@end lilypond
-@refbugs
+@knownissues
When using different time signatures in parallel, the spacing is
aligned vertically, but bar lines distort the regular spacing.
also remove @internalsref{Forbid_line_break_engraver}.
-@refbugs
+@knownissues
Not all durations (especially those containing tuplets) can be
represented exactly with normal notes and dots, but the engraver
@end lilypond
-@commonprop
+@snippets
Beaming patterns may be altered with the @code{beatGrouping} property,
Internals Reference: @internalsref{Beam}.
-@refbugs
+@knownissues
Automatically kneed cross-staff beams cannot be used together with
hidden staves. See @ref{Hiding staves}.
beaming should be switched off with @code{\autoBeamOff}.
-@refcommands
+@predefined
@funindex \autoBeamOff
@code{\autoBeamOff},
@code{\autoBeamOn}.
-@refbugs
+@knownissues
If a score ends while an automatic beam has not been ended and is
still accepting notes, this last beam will not be typeset at all.
@end lilypond
-@commonprop
+@snippets
@node Feathered beams
@subsubsection Feathered beams
The spacing in the printed output represents the
note durations only approximately, but the midi output is exact.
-@refbugs
+@knownissues
The @code{\featherDurations} command only works with very short
music snippets, and when numbers in the fraction are small.
@end lilypond
-@commonprop
+@snippets
@funindex whichBar
@funindex defaultBarType
@end lilypond
-@commonprop
+@snippets
@funindex barNumberVisibility
@cindex bar numbers, regular spacing
Internals Reference: @internalsref{BarNumber}.
-@refbugs
+@knownissues
Bar numbers may collide with the top of the
@internalsref{StaffGroup} bracket, if there is one. To solve
#"grace"}.
-@commonprop
+@snippets
Grace notes may be forced to use align with regular notes
in other staves by setting @code{strict-grace-spacing} to
Internals Reference: @internalsref{GraceMusic}.
-@refbugs
+@knownissues
A multi-note beamed @emph{acciaccatura} is printed without a slash,
and looks exactly the same as a multi-note beamed
Snippets: @lsrdir{Simultaneous,Simultaneous-notes}.
-@refbugs
+@knownissues
Music expressions like @code{<< @{ g8 e8 @} a4 >>} are not printed
accurately. Use @code{<g a>8 <e a>8} instead.
-@refcommands
+@predefined
@funindex \oneVoice
@code{\oneVoice},
@internalsref{RestCollision}.
-@refbugs
+@knownissues
When using @code{merge-differently-headed} with an upstem eighth
or a shorter note, and a downstem half note, the eighth note gets
Internals Reference: @internalsref{PartCombineMusic}, @internalsref{Voice}.
-@refbugs
+@knownissues
When @code{printPartCombineTexts} is set, if the two voices play
the same notes on and off, the part combiner may typeset @code{a2}
@end quotation
-@commonprop
+@snippets
The header and footer are created by the functions make-footer and
make-header, defined in \paper. The default implementations are in
page given the system to put on it.
-@refbugs
+@knownissues
The option right-margin is defined but doesn't set the right margin
yet. The value for the right margin has to be defined adjusting the
This manual: @ref{Selecting notation font size}.
-@refbugs
+@knownissues
@code{layout-set-staff-size} does not change the distance between the
staff lines.
This makes the following 28 measures (assuming 4/4 time) be broken every
4 measures, and only there.
-@refcommands
+@predefined
@code{\break}, and @code{\noBreak}.
@funindex \break
complicated. More details are available in
@c @lsrdir{spacing}
-@refbugs
+@knownissues
Line breaks can only occur if there is a @q{proper} bar line. A note
which is hanging over a bar line is not proper, such as
@code{optimal-page-breaks}. If you are having trouble with the new page
breakers, you can enable the old one as a workaround.
-@refcommands
+@predefined
@funindex \pageBreak
@code{\pageBreak}
@code{\allowPageTurn}, may also be used at top-level, between scores and
top-level markups.
-@refcommands
+@predefined
@funindex \pageTurn
@code{\pageTurn}
@funindex \allowPageTurn
@code{\allowPageTurn}
-@refbugs
+@knownissues
There should only be one @code{Page_turn_engraver} in a score. If there is more
than one, they will interfere with each other.
@internalsref{SeparatingGroupSpanner}.
-@refbugs
+@knownissues
There is no convenient mechanism to manually override spacing. The
following work-around may be used to insert extra space into a score.
@end lilypond
-@commonprop
+@snippets
By default, spacing in tuplets depends on various non-duration
factors (such as accidentals, clef changes, etc). To disregard
@c @lsr{staff,staff-brackets.ly}
@c snippet 137
-@commonprop
+@snippets
More complex nesting can be accomplished using the property
@code{systemStartDelimiterHierarchy}:
@end lilypond
-@commonprop
+@snippets
To change the tempo in the MIDI output without printing anything,
make the metronome marking invisible @example \once \override
output}.
-@refbugs
+@knownissues
Collisions are not checked. If you have notes above the top line
of the staff (or notes with articulations, slurs, text, etc), then
will quote notes (but no rests), together with scripts and
dynamics.
-@refbugs
+@knownissues
Only the contents of the first @code{Voice} occurring in an
@code{\addQuote} command will be considered for quotation, so
c'4^\markup { bla \bold bla }
@end lilypond
-@refcommands
+@predefined
@funindex \textLengthOn
@code{\textLengthOn},
@code{\textLengthOff}.
-@commonprop
+@snippets
@c TODO: put this in the LSR. -vv
By default, these indications do not influence the note spacing.
However, by using the command @code{\textLengthOn}, the widths
c2\startTextSpan b c\stopTextSpan a
@end lilypond
-@refcommands
+@predefined
@funindex textSpannerUp
@code{\textSpannerUp},
@code{\textSpannerNeutral}.
-@commonprop
+@snippets
To print a solid line, use
all.
-@commonprop
+@snippets
@c TODO: to be LSR-ized stuff -vv
Init files: @file{scm/@/new@/-markup@/.scm}.
-@refbugs
+@knownissues
Kerning or generation of ligatures is only done when the @TeX{}
backend is used. In this case, LilyPond does not account for them
Snippets: @lsrdir{Text,Text}
-@refcommands
+@predefined
@funindex \markuplines
@code{\markuplines}
* More about stanzas::
@end menu
-@commonprop
+@snippets
Checking to make sure that text scripts and lyrics are within the margins is
a relatively large computational task. To speed up processing, lilypond does
@rlearning{Vocal ensembles}.
-@refcommands
+@predefined
@code{\melisma}, @code{\melismaEnd}
@funindex \melismaEnd
@c @lsr{vocal,lyric@/-combine.ly}.
-@refbugs
+@knownissues
Melismata are not detected automatically, and extender lines must be
inserted by hand.
I recommend working on one subsection at a time. For each
subsection,
-- check the mundane formatting. Are the headings (@refcommands,
+- check the mundane formatting. Are the headings (@predefined,
@seealso, etc) in the right order?
- add any appropriate index entries.
- check the links in the @seealso section -- links to music
- check the examples and descriptions. Do they still work?
*Do not* assume that the existing text is accurate/complete;
some of the manual is highly out of date.
-- is the material in the @refbugs still accurate?
+- is the material in the @knownissues still accurate?
- process anything on the TODO list on the GDP web site.
- can the examples be improved (made more explanatory), or is
there any missing info? (feel free to ask specific questions
In general, any \set or \override commands should go in the
"select snippets" section, which means that they should go in LSR
and not the .itely file. For some cases, the command obviously
-belongs in the "main text" (ie not inside @refcommands or @seealso
+belongs in the "main text" (ie not inside @predefined or @seealso
or whatever) -- instrument names are a good example of this.
\set Staff.instrumentName = #"foo"
On the other side of this,
projects / lilypond.git / commitdiff