From: Trevor Daniels <t.daniels@treda.co.uk>
Date: Sun, 19 Jan 2014 17:15:23 +0000 (+0000)
Subject: Doc: Issue 3807: More accurate wording for \version instructions
X-Git-Tag: release/2.19.2-1~22
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=2a1dd5d955ab07001ce7e6835966e741bbb99f4a;p=lilypond.git

Doc: Issue 3807: More accurate wording for \version instructions
---

diff --git a/Documentation/contributor/doc-work.itexi b/Documentation/contributor/doc-work.itexi
index c6d8560c0b..55c51bddaf 100644
--- a/Documentation/contributor/doc-work.itexi
+++ b/Documentation/contributor/doc-work.itexi
@@ -70,15 +70,17 @@ encouraged to contact the @ref{Meisters, Documentation Meister}.
 @node version in documentation files
 @section @code{\version} in documentation files
 
-Every documentation file which includes LilyPond code should begin
-with a @code{\version} statement referencing a version of LilyPond
+Every documentation file which includes LilyPond code must begin
+with a @code{\version} statement, since the build procedure
+explicitly tests for its presence and will not continue otherwise.
+The @code{\version} statement should reference a version of LilyPond
 consistent with the syntax of the contained code.
 
-The @code{\version} statement should be commented out to avoid
-creating problems when building releases with GUB, like this:
+Since the @code{\version} statement is not valid Texinfo input it
+must be commented out like this:
 
 @example
-%c \version "2.19.1"
+@@c \version "2.19.1"
 @end example
 
 So, if you are adding LilyPond code which is not consistent with the