+2004-02-27 Heikki Junes <hjunes@cc.hut.fi>
+
+ * input/test/[+c-i]*.ly: refresh descriptions -- maintain
+ impersonal style.
+
2004-02-26 Jan Nieuwenhuizen <janneke@gnu.org>
* scm/define-markup-commands.scm (upright): New markup command.
@section Introduction
This document shows all kinds of tips and tricks, from simple to
-advanced. Here you may also find dirty tricks, or very the very
+advanced. You may also find dirty tricks, or the very very
latest features that have not been documented or fully implemented
yet.
This document is for LilyPond version
\version "2.1.26"
\header {
texidoc = "@cindex Capital Letters
-You can set the font to use small caps.
+The font can be changed to small caps.
" }
shapeSC = \override LyricText #'font-shape = #'caps
\version "2.1.26"
\header{
texidoc="@cindex Cautionary Accidentals
-LilyPond can display cautionary accidentals in different ways.
+Cautinary accidnetals are displayed in slurs by default. They can be
+shown also with accidentals of smaller size.
" }
\score { \notes \context Staff \transpose c c'' {
\key d \major
\version "2.1.26"
\header {
texidoc = "@cindex Chord Names German
-By setting @code{chordRootNamer}, the root
-of the chord may be named with a different function.
-
-Setting @code{\germanChords} gives true german chord-names,
-@code{\semiGermanChords} gives semi-german chord-names - - with Bb and
-keeping the english names.
-
+The english naming of chords (default) can be changed to german
+(@code{\germanChords} replaces B and Bes to H and B) or semi-german
+(@code{\semiGermanChords} replaces B and Bes to H and Bb).
" }
\header {
texidoc = " Chord names are generated from a list pitches. The
-functions constructing the names are customisable. This file shows
-Jazz chords, following Ignatzek (1995), page 17 and 18, Banter chords,
+functions which construct these names can be customised. Here are shown
+Jazz chords, following Ignatzek (pp. 17-18, 1995), Banter chords,
and an alternative Jazz chord notation.
-
"
}
+% There are three references, but only two ways to print chord names?
+% Which refers to where? -HJJ
chs = \notes \transpose c' c'
{
\version "2.1.26"
\header { texidoc= "@cindex Chord Names No Inversions
-Chord names don't attempt to find inversions and
-bass notes. " }
+Since there are several interpretations for recognizing
+chord names, the lowest note is the bass note of a chord and the inversion
+of the chord is found accordingly. " }
scheme = \notes {
<c' e' g'>1
\version "2.1.26"
\header {
-texidoc = "Jazz chords can also be used without notes."
+texidoc = "Jazz chord names can also be printed without notes."
}
\score{
\header {
texidoc = "@cindex Chord Octavation
Appending @code{_8} or @code{^8} to a clef name will
-add an octavation sign to the clef, although the clef
-name needs to be in quotes (such as \"treble^8\").
+add an octavation sign to the clef; then the clef name
+is given in quotes (such as \"treble^8\").
" }
\score {
\header {
texidoc = "@cindex Clef End of Line
-Scales, but with clef and key signature at the end of the line.
+In these scales, the clef and key signature are shown at the end of the line.
" }
\score {
@cindex Clef Manual Control
-You can use the clef engraver by using @code{\property} directly.
-@code{\clef} is merely a front-end to this. All the notes in this
-example are central C."
+The positioning of glyph and note can be separated. @code{\clef} is
+a front-end, which keeps them together. All the notes in this example
+are central C."
}
texidoc = "@cindex Orchestra Score
@cindex Coriolan Score
-Demonstration of how to set up an orchestral score (Beethoven's Coriolan overture).
+In an orchestral score (Beethoven's Coriolan overture), there are
+different instrument groups, and some of the instruments may be
+transposed. Instruments are indicated either with a long or short name.
" }
#(set-global-staff-size 16)
\header{
texidoc="@cindex Count Systems
-Display the number of systems, or the system number of a
-Grob. This can be most useful to assertain that a piece uses a
-specified number of lines.
+The function which controls the printing of the system number may be also
+overridden to print, for example, the number of systems or the system
+number of a grob.
" }
+% Original comment has no sense? -HJJ:
+% This can be most useful to assertain that a piece uses a specified number of lines.
#(define (display-systemno smob)
(let* ((this-system (ly:grob-system smob))
\version "2.1.26"
\header{
texidoc="@cindex Crescendi
-LilyPond can print crescendi in a number of different ways.
+Crescendi can be printed in a number of different ways.
" }
\score{
\notes\relative c''{
% TODO: check to see if this example can be simplified using \small
% or \tiny.
\header { texidoc = "@cindex Cue Notes
-Cue notes should be set in smaller type. "
+Cue notes are typeset in a smaller font. "
% Cue clefs are usually not restored explicitly. "
}
\header {
texidoc = "@cindex Divisiones
Divisiones are gregorian variants of breathing signs.
-Choices are @code{divisioMinima}, @code{divisioMaior}
+Choices are @code{divisioMinima}, @code{divisioMaior},
@code{divisioMaxima} and @code{finalis}, @code{virgula} and
@code{caesura}.
" }
\version "2.1.26"
\header {
texidoc = "@cindex Dynamic Absolute Volume
-Absolute dynamics have effect in MIDI files.
+Absolute dynamics have an effect on MIDI files.
"
}
% probably should be merged into refman.
\header{
texidoc = "@cindex Dynamic Piu Forte
-Additional tricks for dynamics. Pi`u forte dynamic script. " }
+PiĆ¹ forte dynamics is produced using @code{\markup}. " }
piuf = \markup { \italic "pi\\`u" \dynamic "f" }
\version "2.1.26"
% TODO: does this work? It doesn't do anything with 1.7.20
+% Still does not work. 2.1.26 -HJJ
\header {texidoc="@cindex Embedded scm
You can embed scm functions in your scores.
"}
this situation, the accidentals and staff are shared, but the stems,
slurs, beams, etc. are private to each voice. Hence, engravers should
be grouped. The engravers for note head, stems, slurs, etc. go into a
-group called ``Voice context,'' while the engravers for key,
-accidental, bar, etc. go into a group called ``Staff context.'' In the
+group called ``Voice context'', while the engravers for key,
+accidental, bar, etc. go into a group called ``Staff context''. In the
case of polyphony, a single Staff context contains more than one Voice
context. Similarly, more Staff contexts can be put into a single Score
context. "
\version "2.1.26"
\header {
-texidoc = "The notation problem, @emph{what} symbols to create,
+texidoc = "The notation problem, creating a certain symbol,
is handled by plugins. Each plugin is called Engraver. In this example,
- we switch on engravers one by one, in the following order
+engravers is switched on one by one, in the following order:
@itemize
-@item Note heads
-@item Staff symbol
-@item Clef
-@item Stem
-@item Beams, slurs, accents
-@item Accidentals, bar lines, time signature, and key signature.
+@item note heads,
+@item staff symbol,
+@item clef,
+@item stem,
+@item beams, slurs, accents,
+@item accidentals, bar lines, time signature, and key signature.
@end itemize
Engravers are grouped. For example, note heads, slurs, beams etc. form
-a Voice context. Engravers for key, accidental, bar, etc. form the
+a Voice context. Engravers for key, accidental, bar, etc. form a
Staff context.
"
\header{ texidoc="@cindex Staff Extra
@cindex Staff Ossia
-You can add an extra staff after the beginning of a piece. "}
+You can add (possibly temporarily) an extra staff after the beginning of
+a piece. "
+}
\score {
<<
\header
{
texidoc = "An alternate method to make bass figures is to use
-markup texts."
+@code{markup} texts."
}
\version "2.1.26"
% followVoice: connect note heads with line when thread switches staff
\header{ texidoc="@cindex followVoice Voice
-Voices can be traced automagically when they switch staves by setting
-property @code{followVoice}. " }
+Voices can be traced automatically when they switch staves by setting
+@code{followVoice}. " }
\score {
\version "2.1.26"
\header {
texidoc="@cindex Force hshift
-Force hshift to override collisions. " }
+Horizontal shift (@code{hshift}) can be forced in order to avoid collisions. " }
\score {
\notes\relative c'
texidoc="@cindex Gourlay
-This is taken from Gourlay's paper on
-breaking lines. "
+The breaking of line works also with polyphony. This is taken from
+Gourlay's paper on breaking lines. "
}
title = "Gregorian Scripts"
texidoc = "@cindex Gregorian Scripts
-Gregorian Scripts:
+Here is demonstrated a preliminary support of Gregorian Scripts:
ictus, circulus, semicirculus, accentus, episem.
\header {
texidoc ="@cindex Artificial Harmonics
-
-Artificial harmonics are notated with a different notehead style. This
-achieved by marking the harmonic pitch with @code{\harmonic}."
+Artificial harmonics are notated with a different notehead style, by
+marking the harmonic pitch with @code{\harmonic}."
}
High level functionality (eg. conditional defines),
can be accomplished with GUILE.
-This example puts the current version in the tagline via Scheme.
-Since the tagline isn't used in creating the webpage, this example
-doesn't output anything unusual in the collated snippets.
+This example puts the current version in the tagline via Scheme,
+however, the tagline is not printed to the collated webpage snippets.
"
}
\version "2.1.26"
\header { texidoc = "@cindex Horizontal Shift
-You can manually shift notes horizontally. " }
+Notes may be manually horizontally shifted. " }
shiftI = \override NoteColumn #'horizontal-shift = #0
shiftII = \override NoteColumn #'horizontal-shift = #1
\version "2.1.26"
\header { texidoc = "@cindex Incipit
-This shows how to make an ``incipit'' to indicate scordatora
-tuning of a violin part, using the clefStyle property.
-The two first bars of Biber's Rosary sonata III. " }
+This example shows how to make an ``incipit'' to indicate
+scordatora tuning of a violin part, by overriding the @code{style} of
+a @code{TimeSignature}.
+Here are the two first bars of Biber's Rosary sonata III. " }
\version "2.1.26"
\header { texidoc = "@cindex Instrument Name Grandstaff
-You can name the whole grandstaff in addition to individual staffs. " }
+You can have a name for the whole @code{GrandStaff} in addition to
+individual @code{Staff}s. " }
\score {
\notes
\header { texidoc="@cindex Seperate Staccato
You can enter notes and articulations separately, and merge
-them into one thread. Here is an example to add repeated staccato dots."
+them into one thread. In this example, a repead series of staccato dots
+is attached to the notes."
}
staccatos = \notes { s4-. s-. s-. s s }