https://codereview.appspot.com/51450044/diff/1/Documentation/contributor/doc-work.itexi File Documentation/contributor/doc-work.itexi (right):
https://codereview.appspot.com/51450044/diff/1/Documentation/contributor/doc-work.itexi#newcode77 Documentation/contributor/doc-work.itexi:77: The @code{\version} statement should be commented out to avoid Sigh, I just can't keep up with reviewing stuff. This statement is utterly wrong. It's more like A @code{\version} statement is required in all Texinfo documentation files (ending with @samp{.tely} or @samp{.itely}) as well as LilyPond input files (ending with @samp{.ly} or @samp{.ily}) in order to keep track of the current syntax. Its presence is required for building a release. Since the @code{\version} statement is not valid or reasonable input outside of standalone LilyPond files, it will more often than not commented out. In Texinfo, this will be done using @example @@c \version "2.19.1" @end example @code{convert-ly} and GUB will recognize the statement even if commented out. https://codereview.appspot.com/51450044/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
