X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fja%2Fusage%2Flilypond-book.itely;h=0d9e18923e895387fd022f7b961ff7d01fc1ab20;hb=2940cdd12c135ef94e4c95ac815e76014eef9c79;hp=fad18014612ea33cfcab0bc385d38684533a71a0;hpb=3bbcacb6ab56baec5f28fa2e17d575994ab90484;p=lilypond.git

diff --git a/Documentation/ja/usage/lilypond-book.itely b/Documentation/ja/usage/lilypond-book.itely
index fad1801461..0d9e18923e 100644
--- a/Documentation/ja/usage/lilypond-book.itely
+++ b/Documentation/ja/usage/lilypond-book.itely
@@ -8,7 +8,7 @@
     Guide, node Updating translation committishes..
 @end ignore
 
-@c \version "2.13.36"
+@c \version "2.14.0"
 
 @c Translators: Yoshiki Sawada
 @c Translation status: post-GDP
@@ -223,7 +223,7 @@ or
 Additionally, @code{\lilypondversion} displays the current version
 of lilypond.
 Running @command{lilypond-book} yields a file that can be further
-processed with @LaTeX{}. 
+processed with @LaTeX{}.
 
 We show some examples here.  The @code{lilypond} environment
 
@@ -715,12 +715,12 @@ as a domain.
 @item texidoc
 (Only for Texinfo output.)  If @command{lilypond} is called with the
 @option{--header=@/texidoc} option, and the file to be processed is
-called @file{foo@/.ly}, it creates a file @file{foo@/.texidoc} if there
+called @file{foo.ly}, it creates a file @file{foo.texidoc} if there
 is a @code{texidoc} field in the @code{\header}.  The @code{texidoc}
 option makes @command{lilypond-book} include such files, adding its
 contents as a documentation block right before the music snippet.
 
-Assuming the file @file{foo@/.ly} contains
+Assuming the file @file{foo.ly} contains
 
 @example
 \header @{
@@ -748,11 +748,11 @@ Most LilyPond test documents (in the @file{input} directory of the
 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
+@code{@@documentlanguage @var{LANG}} and @file{foo.ly} header
 contains a @code{texidoc@var{LANG}} field, and if @command{lilypond}
 is called with @option{--header=@/texidoc@var{LANG}}, then
-@file{foo@/.texidoc@var{LANG}} will be included instead of
-@file{foo@/.texidoc}.
+@file{foo.texidoc@var{LANG}} will be included instead of
+@file{foo.texidoc}.
 
 @item lilyquote
 (Only for Texinfo output.)  This option is similar to quote, but only
@@ -765,9 +765,9 @@ useful if you want to @code{quote} the music snippet but not the
 (Only for Texinfo output.) This option works similarly to
 @code{texidoc} option: if @command{lilypond} is called with the
 @option{--header=@/doctitle} option, and the file to be processed is
-called @file{foo@/.ly} and contains a @code{doctitle} field in the
-@code{\header}, it creates a file @file{foo@/.doctitle}.  When
-@code{doctitle} option is used, the contents of @file{foo@/.doctitle},
+called @file{foo.ly} and contains a @code{doctitle} field in the
+@code{\header}, it creates a file @file{foo.doctitle}.  When
+@code{doctitle} option is used, the contents of @file{foo.doctitle},
 which should be a single line of @var{text}, is inserted in the
 Texinfo document as @code{@@lydoctitle @var{text}}.
 @code{@@lydoctitle} should be a macro defined in the Texinfo document.