Doc: clean up @file{} entries

[lilypond.git] / Documentation / usage / lilypond-book.itely

diff --git a/Documentation/usage/lilypond-book.itely b/Documentation/usage/lilypond-book.itely
index 80ed297ea2778737a6764b8e8a3283ba160279d3..44b2dc0a265bfdea9608448476b8918a9b790ca2 100644 (file)
--- a/Documentation/usage/lilypond-book.itely
+++ b/Documentation/usage/lilypond-book.itely
@@ -100,8 +100,8 @@ Larger examples can be put into a separate file, and introduced with
 
 \lilypondfile[quote,noindent]{screech-boink.ly}
 
-(If needed, replace screech-boink.ly by any .ly file you put in the same
-directory as this file.)
+(If needed, replace @file{screech@/-boink@/.ly} by any @file{@/.ly} file
+you put in the same directory as this file.)
 
 \end{document}
 @end verbatim
@@ -109,7 +109,7 @@ directory as this file.)
 
 @subheading Processing
 
-Save the code above to a file called @file{lilybook.lytex}, then in a
+Save the code above to a file called @file{lilybook@/.lytex}, then in a
 terminal run
 
 @c keep space after @version{} so TeX doesn't choke
@@ -409,7 +409,7 @@ Additionally, @code{@@lilypondversion} displays the current version
 of lilypond.
 
 When @command{lilypond-book} is run on it, this results in a Texinfo
-file (with extension @file{.texi}) containing @code{@@image} tags for
+file (with extension @file{@/.texi}) containing @code{@@image} tags for
 HTML, Info and printed output.  @command{lilypond-book} generates images
 of the music in EPS and PDF formats for use in the printed output, and
 in PNG format for use in HTML and Info output.
@@ -503,11 +503,11 @@ inline or not inline.  The snippet formatting options are always
 provided in the @code{role} property of the innermost element (see in
 next sections).  Tags are chosen to allow DocBook editors format the
 content gracefully.  The DocBook files to be processed with
-@command{lilypond-book} should have the extension @file{.lyxml}.
+@command{lilypond-book} should have the extension @file{@/.lyxml}.
 
 @subheading Including a LilyPond file
 
-This is the most simple case.  We must use the @file{.ly} extension for
+This is the most simple case.  We must use the @file{@/.ly} extension for
 the included file, and insert it as a standard @code{imageobject}, with
 the following structure:
 
@@ -547,8 +547,8 @@ the @code{programlisting} inside.
 
 @subheading Processing the DocBook document
 
-Running @command{lilypond-book} on our @file{.lyxml} file will create a
-valid DocBook document to be further processed with @file{.xml}
+Running @command{lilypond-book} on our @file{@/.lyxml} file will create a
+valid DocBook document to be further processed with @file{@/.xml}
 extension.  If you use
 @uref{http://@/dblatex@/.sourceforge@/.net@/,dblatex}, it will create a
 PDF file from this document automatically.  For HTML (HTML Help,
@@ -691,7 +691,7 @@ will be printed with a verbatim block like
 If you would like to translate comments and variable names in verbatim
 output but not in the sources, you may set the environment variable
 @code{LYDOC_LOCALEDIR} to a directory path; the directory should
-contain a tree of @file{.mo} message catalogs with @code{lilypond-doc}
+contain a tree of @file{@/.mo} message catalogs with @code{lilypond-doc}
 as a domain.
 
 @item addversion
@@ -716,7 +716,7 @@ Assuming the file @file{foo@/.ly} contains
 @end example
 
 @noindent
-and we have this in our Texinfo document @file{test.texinfo}
+and we have this in our Texinfo document @file{test@/.texinfo}
 
 @example
 @@lilypondfile[texidoc]@{foo.ly@}
@@ -731,7 +731,7 @@ lilypond-book --pdf --process="lilypond \
 @end example
 
 Most LilyPond test documents (in the @file{input} directory of the
-distribution) are small @file{.ly} files which look exactly like this.
+distribution) are small @file{@/.ly} files which look exactly like this.
 
 For localization purpose, if the Texinfo document contains
 @code{@@documentlanguage @var{LANG}} and @file{foo@/.ly} header
@@ -777,9 +777,9 @@ directory part of the file path is stripped.
 @section Invoking @command{lilypond-book}
 
 @command{lilypond-book} produces a file with one of the following
-extensions: @file{.tex}, @file{.texi}, @file{.html} or @file{.xml},
-depending on the output format.  All of @file{.tex}, @file{.texi} and
-@file{.xml} files need further processing.
+extensions: @file{@/.tex}, @file{@/.texi}, @file{@/.html} or @file{@/.xml},
+depending on the output format.  All of @file{@/.tex}, @file{@/.texi} and
+@file{@/.xml} files need further processing.
 
 @subheading Format-specific instructions
 
@@ -817,9 +817,9 @@ ps2pdf yourfile.ps
 @end example
 
 @noindent
-The @file{.dvi} file created by this process will not contain
+The @file{@/.dvi} file created by this process will not contain
  note heads.  This is normal; if you follow the instructions, they
-will be included in the @file{.ps} and @file{.pdf} files.
+will be included in the @file{@/.ps} and @file{@/.pdf} files.
 
 Running @command{dvips} may produce some warnings about fonts; these
 are harmless and may be ignored.  If you are running @command{latex} in