@c duplicated in Key signature and Accidentals
@warning{New users are sometimes confused about accidentals and
-key signatures. In LilyPond, note names are the raw input; key
-signatures and clefs determine how this raw input is displayed.
+key signatures. In LilyPond, note names specify pitches; key
+signatures and clefs determine how these pitches are displayed.
An unaltered note like@tie{}@code{c} means @q{C natural},
regardless of the key signature or clef. For more information,
-see @rlearning{Accidentals and key signatures}.}
+see @rlearning{Pitches and key signatures}.}
@cindex note names, Dutch
@cindex note names, default
ais1 aes aisis aeses
@end lilypond
-A natural will cancel the effect of an accidental or key
-signature. However, naturals are not encoded into the note name
-syntax with a suffix; a natural pitch is shown as a simple note
-name:
+A natural pitch is entered as a simple note name; no suffix is
+required. A natural sign will be printed when needed to cancel
+the effect of an earlier accidental or key signature.
@lilypond[verbatim,quote,relative=2]
a4 aes a2
adding an exclamation mark@tie{}@code{!} after the pitch. A
cautionary accidental (i.e., an accidental within parentheses) can
be obtained by adding the question mark@tie{}@code{?} after the
-pitch. These extra accidentals can also be used to produce
-natural signs.
+pitch.
@lilypond[verbatim,quote,relative=2]
cis cis cis! cis? c c c! c?
@rglos{quarter tone}.
Learning Manual:
-@rlearning{Accidentals and key signatures}.
+@rlearning{Pitches and key signatures}.
Notation Reference:
@ref{Automatic accidentals},
also vary depending on the language:
@quotation
-@multitable {@code{nederlands}} {-s/-sharp} {-ess/-es} {-ss/-x/-sharpsharp} {-essess/-eses}
+@multitable {@code{nederlands}} {-s/--sharp} {-ess/-es} {-ss/-x/--sharpsharp} {-essess/-eses}
@headitem Language
@tab sharp @tab flat @tab double sharp @tab double flat
@item @code{nederlands}
@item @code{deutsch}
@tab -is @tab -es @tab -isis @tab -eses
@item @code{english}
- @tab -s/-sharp @tab -f/-flat @tab -ss/-x/-sharpsharp
- @tab -ff/-flatflat
+ @tab -s/--sharp @tab -f/--flat @tab -ss/-x/--sharpsharp
+ @tab -ff/--flatflat
@item @code{espanol} or @code{español}
@tab -s @tab -b @tab -ss/-x @tab -bb
@item @code{italiano} or @code{français}
The pitches are displayed as if the numeric argument were
given without parentheses/brackets.
-@snippets
-@lilypondfile[verbatim,quote,texidoc,doctitle]
-{forcing-a-clef-symbol-to-be-displayed.ly}
+By default, a clef change taking place at a line break will cause
+the new clef symbol to be printed at the end of the previous line,
+as a @emph{warning} clef, as well as the beginning of the next.
+This @emph{warning} clef can be suppressed.
-@lilypondfile[verbatim,quote,texidoc,doctitle]
-{keep-change-clefs-full-sized.ly}
+@lilypond[verbatim,quote,relative=1]
+\clef treble { c2 c } \break
+\clef bass { c2 c } \break
+\clef alto
+ \set Staff.explicitClefVisibility = #end-of-line-invisible
+ { c2 c } \break
+ \unset Staff.explicitClefVisibility
+\clef bass { c2 c } \break
+@end lilypond
+
+By default, a clef that has previously been printed will not be
+re-printed if the same @code{\clef} command is issued again and
+will be ignored. The the command
+@code{\set Staff.forceClef = ##t} changes this behaviour.
+@lilypond[verbatim,quote,relative=1]
+ \clef treble
+ c1
+ \clef treble
+ c1
+ \set Staff.forceClef = ##t
+ c1
+ \clef treble
+ c1
+@end lilypond
+
+When there is a manual clef change, the glyph of the changed clef
+will be smaller than normal. This behaviour can be overridden.
+
+@lilypond[verbatim,quote,relative=1]
+ \clef "treble"
+ c1
+ \clef "bass"
+ c1
+ \clef "treble"
+ c1
+ \override Staff.Clef.full-size-change = ##t
+ \clef "bass"
+ c1
+ \clef "treble"
+ c1
+ \revert Staff.Clef.full-size-change
+ \clef "bass"
+ c1
+ \clef "treble"
+ c1
+@end lilypond
+
+@snippets
@lilypondfile[verbatim,quote,texidoc,doctitle]
{tweaking-clef-properties.ly}
@ref{Formatting cue notes}.
Installed Files:
-@file{../scm/parser-clef.scm}.
+@file{scm/parser-clef.scm}.
Snippets:
@rlsr{Pitches}.
@rinternals{clef-interface}.
@knownissues
-Ottavation numbers attached to clefs are treated as separate grobs. So
-any @code{\override} done to the @var{Clef} will also need to be
-applied, as a separate @code{\override}, to the @var{ClefModifier}
-grob.
+Ottavation numbers attached to clefs are treated as separate
+grobs. So any @code{\override} done to the @var{Clef} will also
+need to be applied, as a separate @code{\override}, to the
+@var{ClefModifier} grob.
@lilypond[fragment,quote,verbatim,relative=1]
\new Staff \with {
signatures and clefs determine how this raw input is displayed.
An unaltered note like@tie{}@code{c} means @q{C natural},
regardless of the key signature or clef. For more information,
-see @rlearning{Accidentals and key signatures}.}
+see @rlearning{Pitches and key signatures}.}
The key signature indicates the tonality in which a piece is
played. It is denoted by a set of alterations (flats or sharps)
@lilypondfile[verbatim,quote,texidoc,doctitle]
{non-traditional-key-signatures.ly}
+
@seealso
Music Glossary:
@rglos{church mode},
@rglos{scordatura}.
Learning Manual:
-@rlearning{Accidentals and key signatures}.
+@rlearning{Pitches and key signatures}.
Snippets:
@rlsr{Pitches}.
@lilypondfile[verbatim,quote,texidoc,doctitle]
{adding-an-ottava-marking-to-a-single-voice.ly}
+@lilypondfile[verbatim,quote,texidoc,doctitle]
+{modifying-the-ottava-spanner-slope.ly}
+
@seealso
Music Glossary:
@rglos{octavation}.
projects / lilypond.git / blobdiff