+2005-03-19 Graham Percival <gperlist@shaw.ca>
+
+ * 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 <hanwen@xs4all.nl>
* VERSION (PATCH_LEVEL): release 2.5.16
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
* Modifying context plug-ins::
* Layout tunings within contexts::
* Changing context default settings::
-* Defining new contexts::
+* Defining new contexts::
@end menu
@node Creating contexts
* Text encoding::
* Nested scores::
* Overview of text markup commands::
-* New dynamic marks::
+* New dynamic marks::
+* Other text markup issues::
@end menu
@node Text encoding
@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
+
+
\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
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}
@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,
@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
@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.
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
@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
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
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
projects / lilypond.git / commitdiff