Re: [PATCH] Docs: Some adjustments to the AU (we don't produce .tex files!), German translations of some AU sections

[John Mandereau]

On 2008/08/24 21:02 +0200, Reinhold Kainhofer wrote:
> Attached is a patch for the AU, sections 1 and 3, where I

Unless Till has any objection to this way of working, I recommend to
always push chages translations directly to lilypond/translation (or
even both master and lilypond/translation if docs compile succesfully),
because it eases and speeds up proofreading: people who read compiled
docs on your site or relased docs may suggest typo or phrasing fixes,
whereas systematic proofreading of translations before pushing, which
can be done by fewer people, slows down the translation process.

There is also a technical detail: you must not add changes in one
documentation file in English and its update in translations in the same
commit, otherwise check-translation and translation-status scripts
wrongly "complain" the translation isn't up to date (see below); you
must commit the changes in English docs first, then use the committish
you got to update the translations.

$ make CHECKED_FILES=de/user/running.itely check-translation
/usr/bin/python ../buildscripts/check_translation.py ../buildscripts 
de/user/running.itely
diff --git a/Documentation/user/running.itely b/Documentation/user/running.itely
index 06c2186..d2f7c50 100644
--- a/Documentation/user/running.itely
+++ b/Documentation/user/running.itely
@@ -16,7 +16,7 @@
 This chapter details the technicalities of running LilyPond.
 
 @menu
-* Normal usage::                
+* Normal usage::
 * Command-line usage::
 * Error messages::
 * Updating files with convert-ly::
@@ -75,17 +75,17 @@ When invoked with a filename that has no extension, the 
@file{.ly}
 extension is tried first.  To read input from stdin, use a
 dash (@code{-}) for @var{file}.
 
-When @file{filename.ly} is processed it will produce
address@hidden as output (or @file{filename.ps} for PostScript
-output).  If @file{filename.ly} contains more than one @code{\score}
-block, then the rest of the scores will be output in numbered files,
-starting with @file{filename-1.tex}.  Several files can be specified;
+When @file{filename.ly} is processed it will produce @file{filename.ps}
+and @file{filename.pdf} as output.  Several files can be specified;
 they will each be processed independently.  @footnote{The status of
 GUILE is not reset after processing a @code{.ly} file, so be careful
 not to change any system defaults from within Scheme.}
 
-In addition, the value of @code{output-suffix} will be inserted between
-the basename and the number.  An input file containing
+If @file{filename.ly} contains more than one @code{\score}
+block, then the rest of the scores will be output in numbered files,
+starting with @file{filename-1.pdf}.  In addition, the value of
address@hidden will be inserted between the basename and the
+number.  An input file containing
 
 @example
 #(define output-suffix "violin")
@@ -95,8 +95,8 @@ the basename and the number.  An input file containing
 @end example
 
 @noindent
-will output @address@hidden and
address@hidden@file{-cello-1.ps}.
+will output @address@hidden and
address@hidden@file{-cello-1.pdf}.
 
 
 @node Command line options
@@ -460,9 +460,9 @@ A line-break is inserted in the offending line to indicate 
the column
 where the error was found.  For example,
 
 @example
-test.ly:2:19: error: not a duration: 5:
-  @{ c'4 e'5
-             g' @}
+test.ly:2:19: error: not a duration: 5
+  @{ c'4 e'
+           5 g' @}
 @end example
 
 These locations are LilyPond's best guess about where the warning or