@file{EPS} file, without fonts, and as one collated @file{EPS} file with
all pages (systems) including fonts.
-This mode is used by default by lilypond-book.
+This mode is used by default by lilypond-book.
@item svg
for SVG (Scalable Vector Graphics)
@cindex output format, setting
+@item -d,--define-default=@var{var}=@var{val}
+This defines an internal variable @var{var} as the Scheme value
+@var{val}.
+
+Supported values include:
+@table @code
+@item resolution
+set PNG resolution
+@item preview-include-book-title
+include book-titles in preview
+@end table
+
+These settings are returned when calling
+@code{(ly:get-option 'command-line-settings)} from Scheme.
+
@item -h,--help
Show a summary of usage.
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},
-@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.
+(e.g., @file{/usr/share/lilypond})
+should be copied.
If problems arise, the simplest way to trace them down is to run
LilyPond using @command{strace}, which will allow you to determine which
@section Environment variables
+@ignore
For processing both the @TeX{} and the PostScript output, the
appropriate environment variables must be set. The following scripts
do this:
@end table
-
@cindex PostScript
@cindex TEXMF
@cindex printing postscript
-The binary itself recognizes the following environment variables:
+@end ignore
+
+
+@cindex LANG
+@cindex LILYPONDPREFIX
+
+@code{Lilypond} recognizes the following environment variables:
@table @code
@item LILYPONDPREFIX
This specifies a directory where locale messages and
This selects the language for the warning messages.
@end table
-@cindex LANG
-@cindex LILYPONDPREFIX
@node Error messages
@section Error messages
to run
@example
-covert-ly -e myfile.ly
+convert-ly -e myfile.ly
@end example
If there are no changes to myfile.ly and file called myfile.ly.NEW
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
@end ignore
@verbatim
-There are a few things that the convert-ly cannot handle. Here's a list of limitations
-that the community has complained about.
+There are a few things that the convert-ly cannot handle. Here's a
+list of limitations that the community has complained about.
-This bug report structure has been chosen because convert-ly has a structure that doesn't
-allow to smoothly implement all needed changes. Thus this is just a wishlist, placed
-here for reference.
+This bug report structure has been chosen because convert-ly has a
+structure that doesn't allow to smoothly implement all needed changes.
+Thus this is just a wishlist, placed here for reference.
1.6->2.0:
Doesn't always convert figured bass correctly, specifically things like {< >}. Mats' comment on working around this:
problem. Don't forget to tell which version of LilyPond you use! Send
the report to @email{bug-lilypond@@gnu.org}.
+@ignore
+@c the bug database is not up to date enough.
+
When you've found a bug, have a look at our
-@uref{http://@/lilypond@/.org/@/doc/@/v2.3/@/bugs/,bug database} to see if
+@uref{http://@/lilypond@/.org/@/doc/@/v2.5/@/bugs/,bug database} to see if
it has already been reported. You could also try to do a few searches
on the mailing list for the bug. Sometimes the bug will have already
been reported and a fix or workaround is already known.
+@end ignore
Here is an example of a good bug report:
Using Mac OSX 10.3.5, fink package lilypond-unstable
-\version "2.3.22"
+\version "2.5.18"
\relative c''@{
a4 b cis d
@}
@end example
@lilypond[quote]
-\version "2.3.22"
+\version "2.5.18"
\relative c''{
\override Accidental #'extra-offset = #'(1.0 . 0)
a4 b cis d
manuals using Info. If @file{lilypond-mode} is not installed on your
platform, then read the
@ifhtml
-@uref{../../../topdocs/out-www/INSTALL.html,installation instructions}.
+@uref{source/Documentation/topdocs/out-www/INSTALL.html,installation instructions}.
@end ifhtml
@ifnothtml
installation instructions.
For @uref{http://@/www@/.vim@/.org,VIM}, a @file{vimrc} is supplied, along
with syntax coloring tools. For more information, refer to the
@ifhtml
-@uref{../../../topdocs/out-www/INSTALL.html,installation instructions}.
+@uref{source/Documentation/topdocs/out-www/INSTALL.html,installation instructions}.
@end ifhtml
@ifnothtml
installation instructions.
@item JEdit
-The @uref{http://@/www@/.jedit@/.org/,jEdit} editor has a LilyPond plugin.
+The @uref{http://@/www@/.jedit@/.org@/,jEdit} editor has a LilyPond plugin.
This plugin includes a DVI viewer, integrated help and viewing via
GhostScript. It can be installed by doing @key{Plugins > Plugin
Manager}, and selecting @code{LilyTool} from the @key{Install} tab.
projects / lilypond.git / blobdiff