+2004-02-27 Heikki Junes <hjunes@cc.hut.fi>
+
+ * input/test/[j-o]*.ly: update texidocs.
+
2004-02-27 Jan Nieuwenhuizen <janneke@gnu.org>
* scm/documentation-generate.scm (usermanref): Add macro for TeX.
opus = "opus"
piece = "piece"
poet = "poet"
-texidoc = "This file tests lilypond titling. It should be processed with lilypond. "
+texidoc = "In the generated output for printing, there are several titles which do not appear in the web pages. "
%
% todo: check whether title.ly does the same. --hwn
\header {
-texidoc = "In tight situations, hyphens are removed, except at the
-end of the line. Normally, lyrics aren't set this tight, but by
-tuning down @code{padding} of in @code{SeparationItem}, syllables are put closer together, and hyphens may disappear.
-
-In some languages (eg. German and Hungarian). hyphens should not
-disappear, since spelling depends on hyphenation. In this case,
-hyphens can be forced to remain by setting @code{minimum-length} on
-the LyricHyphen grob.
+texidoc = "In tightly engraved music, hyphens are removed, except at the
+end of the line. Normally, lyrics are not typeset so tightly, but by
+tuning down @code{padding} of in @code{SeparationItem}, syllables are put
+closer together, and as a result hyphens may disappear.
+
+In some languages (e.g. German and Hungarian), hyphens should not
+disappear, since spelling depends on hyphenation. For that purpose,
+hyphens can be forced to remain by overriding @code{minimum-length} of
+the @code{LyricHyphen} grob.
"
}
{
texidoc ="
-By inserting @code{\\skip} statements into lyric lines, one can put less lyric syllables to a melody.
+By inserting @code{\\skip} statements into lyric lines, one can attach
+less lyric syllables to a melody.
"
}
% check with ancient- stuff. rename, merge, something. -gp
\header { texidoc = "@cindex Ancient Mensural Ligatures
-LilyPond can print mensural ligatures."
+In mensural ligatures, notes with ancient durations are printed
+in a tight manner."
}
\version "2.1.26"
% candidate for regression. -gp
\header {
- texidoc="MIDI and midi2ly test file. Diff between this and midi2ly.py should be minimal."
+ texidoc="Converting LilyPond input to MIDI and then again back with
+ @code{midi2ly.py} is a reversible procedure in some simple cases,
+ which mean that the original @code{.ly} -file and the one converted
+ back from the generated @code{.midi} -file do not differ.
+ Here are produced some scales.
+
+ "
}
%{
% possible rename to scheme- or something like that. -gp
\header { texidoc= "@cindex Scheme Manual Accidentals
-Positions of accidentals may be manually set. This
-involves some scheme code. " }
+The positions of accidentals may be manually set by incorporating
+some Scheme code. " }
#(define (make-acc-position-checker pos)
(lambda (elt)
\version "2.1.26"
% possible rename to scheme- or something like that. -gp
\header { texidoc = "@cindex Scheme Move Text
-You can move objects around with scheme. This example shows how to
-move text around. " }
+Objects, like text, can be moved around by using some Scheme code.
+" }
#(define (make-text-checker text)
(lambda (grob) (equal? text (ly:grob-property grob 'text))))
% possible rename to scheme- something. -gp
\header { texidoc = "@cindex Scheme Music Creation
-You can create music expressions from Scheme. The
-mechanism for this is rather clumsy to use, so avoid it if possible. "
+You can engrave music using just Scheme expressions. Although those
+expressions reflect the inner mechanism of LilyPond, they are rather
+clumsy to use, so avoid them, if possible. "
}
#(define (make-note-req p d)
\version "2.1.26"
\header{ texidoc="@cindex Nested Staff Groups
-LilyPond can print nested groups of staffs. "
+Staffs can be nested in various combinations. Here, @code{StaffGroup}
+and @code{ChoirStaff} produce similar straight brackets, whereas
+@code{GrandStaff} produces curly brackets. In @code{InnerStaffGroup}
+and @code{InnerChoirStaff}, the brackets are shifted leftwards.
-% old texidoc; it sounds like a testing comment, rather than an "example" comment.
-%In InnerStaffGroup and InnerChoirStaff, the brackets should be shiftet leftwards.
-}
+"
\score { \notes
<<
>>
\new ChoirStaff <<
\new Staff {c' d' e' f'}
- \new InnerStaffGroup <<
+ \new InnerChoirStaff <<
\new Staff {c' d' e' f'}
\new Staff {c' d' e' f'}
>>
% possible rename to bar-lines-foo. -gp
\header{ texidoc = "@cindex Bar Lines Remove
-You can stop LilyPond from printing bar lines by removing the engraver. "
+Engravers can be removed one by one. Here, the time signature and bar lines
+have been removed.
+"
}
\score {
% possible rename to staff-something. -gp
\header{ texidoc = "@cindex Staff Remove
-You can stop LilyPond from printing the staff by removing the engraver. "
+The printing of the staff lines may be suppressed by removing the
+corresponding engraver.
+"
}
\score {
-\header { texidoc = "A temporary ossia in an instrumental part for
- just a few bars on a separate staff. Here is an example using
- proper short staffs. A simpler solution is to instantiate a full
- staff, and let @code{RemoveEmptyStaffContext} take out the unused parts.
-
- Both solutions are demonstrated here.
+\header { texidoc = "A temporary ossia in an instrumental part may
+ be printed using a separate, short staff. A simpler solution is
+ also given: instantiate a full staff, and let
+ @code{RemoveEmptyStaffContext} take out the unused parts.
" }
\version "2.1.26"
projects / lilypond.git / commitdiff