version that you are working on. See TRANSLATION for details.
@end ignore
+@c \version "2.11.38"
+
@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
under heavy development.
+FIXME: add comments
+@verbatim
+% %{
+@end verbatim
+to 3.1.
+
@menu
* Input files::
* Common syntax issues TODO name?::
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}.
-
-@seealso
-
-Examples: @c @lsr{non-notation,clip-systems.ly}
+For more information on output formats, see @rprogram{Invoking LilyPond}.
@node Including LilyPond files
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
@end example
-@seealso
-
-@c @lsr{text,utf-8.ly}
-
-
@node Different editions from one source
@subsection Different editions from one source
@end example
would yield
-@lilypondfile[ragged-right,quote]{tag-filter.ly}
+@c FIXME: broken
+@c @lilypondfile[ragged-right,quote]{tag-filter.ly}
The arguments of the @code{\tag} command should be a symbol
(such as @code{#'score} or @code{#'part}), followed by a
@end example
-@seealso
-
-Examples: @c @lsr{parts,tag@/-filter@/.ly}
-
-
@knownissues
Multiple rests are not merged if you create the score with both tagged
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.
also mention the typical \fooDown, \fooNeutral predefined commands.
+also mention that some directions are (without other tweaking)
+always up or always down (like dynamics or fermata), while other
+things can alternate between up or down based on the stem direction
+(like slurs or accents).
+
@node Distances and measurements MAYBE MOVE
@subsection Distances and measurements MAYBE MOVE
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 ?
-
-