@node Input syntax
@chapter Input syntax
-This section deals with general lilypond input syntax issues,
+This section deals with general LilyPond input syntax issues,
rather than specific notation.
FIXME: don't complain about anything in this chapter. It's still
* Input files::
* Common syntax issues TODO name?::
* Other stuffs TODO move?::
-* add to a Tweaks chapter::
@end menu
the output. This can be compared to clipping a piece of a paper score
with scissors.
-This is done by definining the measures that need to be cut out
+This is done by defining the measures that need to be cut out
separately. For example, including the following definition
@code{-dclip-systems}. The clips are output as EPS files, and are
converted to PDF and PNG if these formats are switched on as well.
-For more information on output formats, see @rprogram{Invoking lilypond}.
+For more information on output formats, see @rprogram{Invoking LilyPond}.
@seealso
The initialization of LilyPond is done in a number of files that are
included by default when you start the program, normally transparent to the
-user. Run lilypond --verbose to see a list of paths and files that Lily
+user. Run @code{lilypond --verbose} to see a list of paths and files that Lily
finds.
Files placed in directory @file{PATH/TO/share/lilypond/VERSION/ly/} (where
option when invoking @code{lilypond --include=DIR} which adds DIR to the
search path.
-The @code{\include} statement can use full path information, but with the Unix
+The @code{\include} statement can use full path information, but with the UNIX
convention @code{/} rather than the DOS/Windows @code{\}. For example,
if @file{stuff.ly} is located one directory higher than the current working
directory, use
TODO: everything
-By default, lilypnod does a pretty jazz'n job of picking
+By default, LilyPond does a pretty jazz'n job of picking
directions. But in some cases, it may be desirable to force a
direction.
brief
description of what they do (perhaps also with a note about what
default
-behaviour is associated with each of them, but this may be
+behavior is associated with each of them, but this may be
unmanageable),
should be there, and then we could simply list the remaining ones
without
\fretmode ?
-
-@node add to a Tweaks chapter
-@section add to a Tweaks chapter
-
-@menu
-* Line styles::
-@end menu
-
-@node Line styles
-@subsection Line styles
-
-Valentin: write stuff here.
-
-
-