2004-02-28 Heikki Junes <hjunes@cc.hut.fi>
+ * input/test/[t-v]*.ly: finish rewriting texidocs.
+
+ * input/test/vaticana.ly: remove.
+ * input/test/ligature-vaticana.ly: new, renamed file name.
+
* input/test/stem-centered.ly: remove.
* input/test/mensural-note-heads.ly: new file. take content from
removed file stem-centered.ly.
\version "2.1.26"
\header {texidoc = "@cindex Tablature hammer
-You can fake a hammer in tablature with slurs. "
+A hammer in tablature can be faked with slurs. "
}
\score{
\version "2.1.26"
\header{ texidoc = "@cindex Tabulature
-A sample tablature, with both normal staff and tab.
+Tablature is internally done by overriding the note-head formatting function
+and let it act on a 6-line staff. A special engraver takes then care of
+choosing the fret and converting the pitch to a number.
-Tablature is done by overriding the note-head formatting function, and
-putting it on a 6-line staff. A special engraver takes care of going
-from string-number + pitch to number. "
+Thus, by providing the fret numbers, the same music can be generated both
+for a normal and tabulature staffs. By default, the fret is the smallest
+possible, according to @code{minimumFret}.
+
+"
}
partition = \notes {
texidoc= "
An additional stave can be typeset in the middle of a score line.
-A new context type is created to avoid printing time and key
-signatures and clef at the beginning of the temporary stave.
+A new context type is created for the temporary staff to avoid printing
+time and key signatures and clef at the beginning of the extra stave.
"
}
@cindex rotated text
@cindex choir, rotated text
-Rotated text may be faked using inline TeX (or inline
-postscript). To see the result, this files must be processed with
-the lilypond.py script, and a line must be uncommented.
+Inline TeX (or PostScript) may be used, for example, to rotate text.
+To see the result, use the @code{lilypond.py} script to generate the
+output for printing of the source of this example (commenting one line).
"
\version "2.1.26"
\header { texidoc = "@cindex text spanner
-You can make LilyPond print text spanners. "
+Text spanners can be used in the similar manner than markings for pedals
+or octavation.
+"
}
\score{
\version "2.1.26"
\header { texidoc = "@cindex Textscript
-Test font selection and scm text markup. "
+There are different fonts and glyphs to be used with @code{\markup} command. "
}
\score{
\header {
- texidoc = "Cross voice ties can be faked by blanking noteheads."
+ texidoc = "Cross voice ties can be faked by using transparent noteheads."
}
\version "2.1.26"
\header { texidoc = "@cindex Tie Sparse
-Setting sparseTies causes only one tie to be
-generated per chord pair. "
+Setting @code{sparseTies} generated only one tie per chord pair. "
}
+
+% seem not to work -HJJ
\score {
\context Voice \notes\relative c {
Double time
-signatures are not supported explicitly, but can be faked with markups
-and overriding formatting routines. " }
+signatures are not supported explicitly, but they can be faked with
+markups and overriding formatting routines. " }
tsMarkup =
\markup {
\header { texidoc = "@cindex Time
-Old time signatures. For further information, consult the file.
+The different styles for time signatures are shown in this file.
"
}
\header{ texidoc = "@cindex Bar Length
-You can alter the length of bars by setting
+You can alter the length of bars by setting explicitly
@code{measureLength} or by resetting @code{measurePosition}. "
}
enteredby = "jcn"
source = "urtext"
- texidoc ="This test lilypond titling. process with lilypond, not lilypond-book."
+ texidoc ="This example tests titling. By processing with @code{lilypond}
+ (not @code{lilypond-book}), you will see all the titles."
}
\score {
\header {
texidoc = "@cindex To XML"
texidoc = #(string-append
- "The input representation is very generic. It
+ "The input representation is very generic. Therefore, it
should not be hard to convert it to XML or a similar format:\n\n"
"@example\n"
\version "2.1.26"
\header{ texidoc = "@cindex Transposition
-Transposition test file."
+Transposing has also an effect key signature, if it is given using
+@code{\key}. If @code{keySignature} is set explicitly instead,
+the key signature is not transposed."
-
-% huh what's this supposed to test?
}
-
+% should the explicitly set key signature transpose also? -HJJ
vOne = \notes \relative c''{
\clef"violin"
\version "2.1.26"
\header { texidoc="@cindex Trill
-Show trill line type.
-
-The extended trill is a TextSpanner in @code{trill} style.
+The extended trill may be produced using @code{TextSpanner} with @code{trill}
+spanner style.
"
}
\header {
texidoc="@cindex Trills
-Document trills, pralls and turns."
+Trills, pralls and turns may also be written out in full. Here the
+D'Anglebert system (1689) is shown."
}
% regression. -gp
\header {
-texidoc = "The standard function unfold-repeats will recursively unfold
-all repeats for correct MIDI output. Thanks to Rune Zedeler."
+texidoc = "Applying the standard function @code{unfold-repeats} unfolds
+recursively all repeats for a correct MIDI output."
}
texidoc = #(string-append "By putting the output of
- @code{lilypond-version} into a lyric, we can print the version
- number in a score, or a lilypond-book document. Another option is
- to append the version to the doc-string, like this: "
+ @code{lilypond-version} into a lyric, it is possible to print the
+ version number of LilyPond in a score, or in a document generated
+ with @code{lilypond-book}. Another possibility is to append the
+ version number to the doc-string, in this manner: "
(lilypond-version)
)
% TODO: huh? what's this file about? -gp
\header { texidoc = "
-Vertical extents may be overriden by
-minimumVerticalExtent, extraVerticalExtent, and verticalExtent. These are
-normal property values, and are written into the grob when the
-associated context finishes, so using it in \property works.
+Vertical extents may increased by setting @code{minimumVerticalExtent},
+@code{extraVerticalExtent}, and @code{verticalExtent}. In this example,
+@code{verticalExtent} is increased.
" }
\score {