Tweaking clef properties: Difference between revisions

Line 1:

Changing the clef glyph, its position, or the ottavation does not change the position of subsequent notes on the staff. To get key signatures on their correct staff lines, <code>middleCClefPosition</code> must also be specified, with positive or negative values moving ~~''middle C''~~ up or down respectively, relative to the staff's center line.

Changing the clef glyph, its position, or the ottavation does not change the position of subsequent notes on the staff. To get key signatures on their correct staff lines, <code>middleCClefPosition</code> must also be specified, with positive or negative values moving “middle C” up or down respectively, relative to the staff's center line.

For example, <code>\clef "treble_8"</code> is equivalent to setting the <code>clefGlyph</code>, <code>clefPosition</code> (the vertical position of the clef itself on the staff), <code>middleCPosition</code>, and <code>clefTransposition</code>. Note that when any of these properties (except <code>middleCPosition</code>) are changed a new clef symbol is printed.

For example, <code>\clef "treble_8"</code> is equivalent to setting the context properties <code>clefGlyph</code>, <code>clefPosition</code> (the vertical position of the clef itself on the staff), <code>middleCPosition</code>, and <code>clefTransposition</code>. Note that when any of these properties (except <code>middleCPosition</code>) are changed a new clef symbol is printed.

The following examples show the possibilities when setting these properties manually. On the first line, the manual changes preserve the standard relative positioning of clefs and notes, whereas on the second line, they do not.

{

% The default treble clef

Line 62:

c'1

}

~~\paper { tagline = ##f }~~

</lilypond>

@@ Line 1: / Line 1: @@
-Changing the clef glyph, its position, or the ottavation does not change the position of subsequent notes on the staff. To get key signatures on their correct staff lines, <code>middleCClefPosition</code> must also be specified, with positive or negative values moving ''middle C'' up or down respectively, relative to the staff's center line.
+Changing the clef glyph, its position, or the ottavation does not change the position of subsequent notes on the staff. To get key signatures on their correct staff lines, <code>middleCClefPosition</code> must also be specified, with positive or negative values moving “middle&nbsp;C” up or down respectively, relative to the staff's center line.
-For example, <code>\clef &quot;treble_8&quot;</code> is equivalent to setting the <code>clefGlyph</code>, <code>clefPosition</code> (the vertical position of the clef itself on the staff), <code>middleCPosition</code>, and <code>clefTransposition</code>. Note that when any of these properties (except <code>middleCPosition</code>) are changed a new clef symbol is printed.
+For example, <code>\clef &quot;treble_8&quot;</code> is equivalent to setting the context properties <code>clefGlyph</code>, <code>clefPosition</code> (the vertical position of the clef itself on the staff), <code>middleCPosition</code>, and <code>clefTransposition</code>. Note that when any of these properties (except <code>middleCPosition</code>) are changed a new clef symbol is printed.
 The following examples show the possibilities when setting these properties manually. On the first line, the manual changes preserve the standard relative positioning of clefs and notes, whereas on the second line, they do not.
-<lilypond version="2.24" full>
+<lilypond version="2.24">
 {
    % The default treble clef
@@ Line 62: / Line 62: @@
    c'1
 }
-\paper { tagline = ##f }
 </lilypond>