From: Graham Percival Date: Sun, 20 Mar 2005 02:58:39 +0000 (+0000) Subject: Misc small changes. X-Git-Tag: release/2.5.17~51 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=5aec80874029722a764f8f88a5eab78702b91135;p=lilypond.git Misc small changes. --- diff --git a/ChangeLog b/ChangeLog index 481de4da71..8ffd55b4bb 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,24 @@ +2005-03-19 Graham Percival + + * Documentation/user/global.itely: added info about naming + identifiers and breakbefore. + + * Documentation/user/invoking.itely: added info about batch + processing files with convert-ly, removed references to TeX + in the jail section. + + * Documentation/user/examples.itely: possibly fixed piano + dynamics. + + * Documentation/user/advanced-notation.itely: added info + about removing other types of Staff. + + * Documentation/user/instrument-notation.itely: possibly + fixed piano staff line switch. + + * Documentation/user/changing-defaults.itely: added info + about using normal font in titles. + 2005-03-18 Han-Wen Nienhuys * VERSION (PATCH_LEVEL): release 2.5.16 diff --git a/Documentation/user/advanced-notation.itely b/Documentation/user/advanced-notation.itely index c44bffb89d..3400c08b01 100644 --- a/Documentation/user/advanced-notation.itely +++ b/Documentation/user/advanced-notation.itely @@ -911,13 +911,14 @@ The first system shows all staves in full. If empty staves should be removed from the first system too, set @code{remove-first} to false in @internalsref{RemoveEmptyVerticalGroup}. +To remove other types of contexts, use @code{\AncientRemoveEmptyStaffContext} +or @code{\RemoveEmptyRhythmicStaffContext}. + Another application is making ossia sections, i.e., alternative melodies on a separate piece of staff, with help of a Frenched staff. See @inputfileref{input/@/test,ossia@/.ly} for an example. - - @node Quoting other voices @subsection Quoting other voices diff --git a/Documentation/user/changing-defaults.itely b/Documentation/user/changing-defaults.itely index b0497e7d0d..d77d08fd31 100644 --- a/Documentation/user/changing-defaults.itely +++ b/Documentation/user/changing-defaults.itely @@ -118,7 +118,7 @@ Translation @arrow{} Context. * Modifying context plug-ins:: * Layout tunings within contexts:: * Changing context default settings:: -* Defining new contexts:: +* Defining new contexts:: @end menu @node Creating contexts @@ -1547,7 +1547,8 @@ Syntax errors for markup mode are confusing. * Text encoding:: * Nested scores:: * Overview of text markup commands:: -* New dynamic marks:: +* New dynamic marks:: +* Other text markup issues:: @end menu @node Text encoding @@ -1656,4 +1657,20 @@ boxf = \markup{ \bracket { \dynamic f } } @end lilypond +@node Other text markup issues +@subsection Other text markup issues + +To use a normal font within a title, you must define it manually + +@example +#(def-markup-command (normal-font layout props arg) (markup?) + "Switch to normal text font" + (interpret-markup layout (cons '((font-series . 'medium) (font-shape . 'upright)) props) arg)) + +\header@{ + title = \markup@{ ABCD \normal-font ABCD @} +@} +@end example + + diff --git a/Documentation/user/examples.itely b/Documentation/user/examples.itely index db4abaf69a..b1226f5299 100644 --- a/Documentation/user/examples.itely +++ b/Documentation/user/examples.itely @@ -411,13 +411,18 @@ pedal = { \override VerticalAlignment #'forced-distance = #7 } } +} +\score { + \context PianoStaff << + \context Staff=upper << \upper \dynamics >> + \context Staff=lower << \lower \dynamics >> + \context Dynamics=pedal \pedal + >> \midi { \context { \type "Performer_group_performer" \name Dynamics \consists "Piano_pedal_performer" - \consists "Span_dynamic_performer" - \consists "Dynamic_performer" } \context { \PianoStaff diff --git a/Documentation/user/global.itely b/Documentation/user/global.itely index 729367d3ca..4aadd5287e 100644 --- a/Documentation/user/global.itely +++ b/Documentation/user/global.itely @@ -645,6 +645,15 @@ a line break. Page breaks are computed by the @code{page-breaking} function in the @code{\paper} block. +To force a new page for a new piece (in a collection of pieces or a +piece in several movements), use @code{breakbefore} in the header. + +@example +\header@{ + breakbefore = ##t +@} +@end example + @refcommands @cindex @code{\pageBreak} @@ -774,7 +783,7 @@ Name of the piece, flush-left below the instrument. @cindex page breaks, forcing @item breakbefore - This forces the title to start on a new page. + This forces the title to start on a new page (set to ##t or ##f). @end table Here is a demonstration of the fields available, @@ -939,7 +948,8 @@ This behavior can be changed by setting the variable @code{toplevel-book-handler} at toplevel. The default handler is defined in the init file @file{scm/@/lily@/.scm}. -@item A compound music expression, such as +@item +A compound music expression, such as @example @{ c'4 d' e'2 @} @end example @@ -952,7 +962,8 @@ This behavior can be changed by setting the variable @code{toplevel-music-handler} at toplevel. The default handler is defined in the init file @file{scm/@/lily@/.scm}. -@item A markup text, a verse for example +@item +A markup text, a verse for example @example \markup @{ 2. The first line verse two. @@ -962,12 +973,15 @@ defined in the init file @file{scm/@/lily@/.scm}. Markup texts are rendered above, between or below the scores or music expressions, wherever they appear. -@item An indentifier, such as +@item +An indentifier, such as @example foo = @{ c4 d e d @} @end example -This can be used later on in the file by entering @code{\foo}. +This can be used later on in the file by entering @code{\foo}. The +name of an identifier should have alphabetic characters only; no +numbers, underscores or dashes. @end itemize diff --git a/Documentation/user/instrument-notation.itely b/Documentation/user/instrument-notation.itely index 1af1186f95..705f44a93c 100644 --- a/Documentation/user/instrument-notation.itely +++ b/Documentation/user/instrument-notation.itely @@ -240,14 +240,14 @@ can be printed automatically. This is switched on by setting @code{followVoice} to true @lilypond[quote,raggedright,fragment,relative=1,verbatim] -\context PianoStaff << - \set followVoice = ##t - \context Staff \context Voice { +\new PianoStaff << + \context Staff=one { + \set followVoice = ##t c1 \change Staff=two b2 a } - \context Staff=two { \clef bass \skip 1*2 } + \context Staff=two { \clef bass \skip 1*2 } >> @end lilypond diff --git a/Documentation/user/invoking.itely b/Documentation/user/invoking.itely index 8025422421..b03c966f90 100644 --- a/Documentation/user/invoking.itely +++ b/Documentation/user/invoking.itely @@ -213,11 +213,17 @@ be a single directory writable by this user, which should be passed in LilyPond needs to read a number of files while running. All these files are to be copied into the jail, under the same path they apper in the real root filesystem. The entire content of the LilyPond installation -(e.g., @file{/usr/share/lilypond}), and the content of the @file{fonts}, +(e.g., @file{/usr/share/lilypond}) +should be copied. + +@ignore +FIXME: fact-check; delete very soon. -gp +, and the content of the @file{fonts}, @file{dvips} and @file{web2c} directories of the @TeX{} installation (usually under @file{/usr/share/texmf}) should be copied, too. If your @TeX{} installation uses @file{ls-R} caches, copy also the cache inside the root of the installation. +@end ignore If problems arise, the simplest way to trace them down is to run LilyPond using @command{strace}, which will allow you to determine which @@ -415,6 +421,14 @@ To upgrade LilyPond fragments in texinfo files, use convert-ly --from=... --to=... --no-version *.itely @end example +To upgrade many files at once, combine @code{convert-ly} with +standard unix commands. This example will upgrade all @code{.ly} +files in the current directory + +@example +for f in *.ly; do convert-ly -e $f; done; +@end example + In general, the program is invoked as follows: @example