From cc9e882dd7c6e3553da51aea22ed253dcf50b21c Mon Sep 17 00:00:00 2001
From: Graham Percival <graham@percival-music.ca>
Date: Mon, 13 Aug 2007 19:21:56 -0700
Subject: [PATCH] convert-ly on the docs.

---
 Documentation/user/README.txt              |  2 +-
 Documentation/user/advanced-notation.itely |  4 +-
 Documentation/user/non-music.itely         |  2 +-
 Documentation/user/putting.itely           |  8 ++--
 Documentation/user/templates.itely         | 44 +++++++++++-----------
 Documentation/user/tutorial.itely          |  4 +-
 Documentation/user/working.itely           |  4 +-
 7 files changed, 34 insertions(+), 34 deletions(-)

diff --git a/Documentation/user/README.txt b/Documentation/user/README.txt
index e736fd6718..7c28e2bc7e 100644
--- a/Documentation/user/README.txt
+++ b/Documentation/user/README.txt
@@ -1,7 +1,7 @@
 Info for Documentation
 ----------------------
 
-Current version of the manual: 2.11.15
+Current version of the manual: 2.11.28
 *** Please update this whenever you run convert-ly on the docs.
 
 convert-ly -e --from=... --to=... --no-version *.itely
diff --git a/Documentation/user/advanced-notation.itely b/Documentation/user/advanced-notation.itely
index 5a7a93f77d..214d1c80a3 100644
--- a/Documentation/user/advanced-notation.itely
+++ b/Documentation/user/advanced-notation.itely
@@ -1092,11 +1092,11 @@ setting @code{break-align-symbol}
 c1
 \key cis \major
 \clef alto
-\override Score.RehearsalMark #'break-align-symbol = #'key-signature
+\override Score.RehearsalMark #'break-align-symbols = #'(key-signature)
 \mark "on-key"
 cis
 \key ces \major
-\override Score.RehearsalMark #'break-align-symbol = #'clef
+\override Score.RehearsalMark #'break-align-symbols = #'(clef)
 \clef treble
 \mark "on clef"
 ces
diff --git a/Documentation/user/non-music.itely b/Documentation/user/non-music.itely
index 853df046ee..6462f4122c 100644
--- a/Documentation/user/non-music.itely
+++ b/Documentation/user/non-music.itely
@@ -49,7 +49,7 @@ these files end with @samp{.ly}.
 A basic example of a lilypond input file is
 
 @example
-\version "2.11.15"
+\version "2.11.23"
 \score @{
   @{ @}     % this is a single music expression;
             % all the music goes in here.
diff --git a/Documentation/user/putting.itely b/Documentation/user/putting.itely
index f715c8c0c1..8090efd6df 100644
--- a/Documentation/user/putting.itely
+++ b/Documentation/user/putting.itely
@@ -35,7 +35,7 @@ cello.  In this case, we would start with @q{Notes and lyrics} (for the
 soprano part).
 
 @example
-\version "2.11.15"
+\version "2.11.23"
 melody = \relative c' @{
   \clef treble
   \key c \major
@@ -64,7 +64,7 @@ text = \lyricmode @{
 Now we want to add a cello part.  Let's look at the @q{Notes only} example:
 
 @example
-\version "2.11.15"
+\version "2.11.23"
 melody = \relative c' @{
   \clef treble
   \key c \major
@@ -100,7 +100,7 @@ normally use bass clef.  We'll also give the cello some different
 notes.
 
 @example
-\version "2.11.15"
+\version "2.11.23"
 sopranoMusic = \relative c' @{
   \clef treble
   \key c \major
@@ -170,7 +170,7 @@ This looks a bit messy; the indentation is messed up now.  That is
 easily fixed.  Here's the complete soprano and cello template.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 sopranoMusic = \relative c' {
   \clef treble
   \key c \major
diff --git a/Documentation/user/templates.itely b/Documentation/user/templates.itely
index 56231eded8..e09a6bdb16 100644
--- a/Documentation/user/templates.itely
+++ b/Documentation/user/templates.itely
@@ -35,7 +35,7 @@ instrument or a melodic fragment.  Cut and paste this into a file,
 add notes, and you're finished!
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 melody = \relative c' {
    \clef treble
    \key c \major
@@ -60,7 +60,7 @@ automatic beaming, you'll have to change or comment out the relevant
 line.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 melody = \relative c' {
    \clef treble
    \key c \major
@@ -91,7 +91,7 @@ text = \lyricmode {
 Want to prepare a lead sheet with a melody and chords?  Look no further!
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 melody = \relative c' {
    \clef treble
    \key c \major
@@ -124,7 +124,7 @@ harmonies = \chordmode {
 This template allows you to prepare a song with melody, words, and chords.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 melody = \relative c' {
    \clef treble
    \key c \major
@@ -165,7 +165,7 @@ harmonies = \chordmode {
 Here is a simple piano staff.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 upper = \relative c'' {
    \clef treble
    \key c \major
@@ -199,7 +199,7 @@ Here is a typical song format: one staff with the melody and lyrics, with
 piano accompaniment underneath.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 melody = \relative c'' {
    \clef treble
    \key c \major
@@ -255,7 +255,7 @@ Instead of having a full staff for the melody and lyrics, you can place
 the lyrics between the piano staff (and omit the separate melody staff).
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 upper = \relative c'' {
    \clef treble
    \key c \major
@@ -302,7 +302,7 @@ since the template is right here, you don't have to do the
 tweaking yourself.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 upper = \relative c'' {
   \clef treble
   \key c \major
@@ -397,7 +397,7 @@ This template demonstrates a string quartet.  It also uses a @code{\global}
 section for time and key signatures.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 
 global= {
   \time 4/4
@@ -457,7 +457,7 @@ contains all the music definitions.  The other files -- @code{score.ly},
 
 @verbatim
 %%%%% piece.ly
-\version "2.11.15"
+\version "2.11.23"
 
 global= {
   \time 4/4
@@ -503,7 +503,7 @@ music = {
 
 
 %%%%% score.ly
-\version "2.11.15"
+\version "2.11.23"
 \include "piece.ly"
 #(set-global-staff-size 14)
 \score {
@@ -514,7 +514,7 @@ music = {
 
 
 %%%%% vn1.ly
-\version "2.11.15"
+\version "2.11.23"
 \include "piece.ly"
 \score {
   \keepWithTag #'vn1 \music
@@ -523,7 +523,7 @@ music = {
 
 
 %%%%% vn2.ly
-\version "2.11.15"
+\version "2.11.23"
 \include "piece.ly"
 \score {
   \keepWithTag #'vn2 \music
@@ -532,7 +532,7 @@ music = {
 
 
 %%%%% vla.ly
-\version "2.11.15"
+\version "2.11.23"
 \include "piece.ly"
 \score {
   \keepWithTag #'vla \music
@@ -541,7 +541,7 @@ music = {
 
 
 %%%%% vlc.ly
-\version "2.11.15"
+\version "2.11.23"
 \include "piece.ly"
 \score {
   \keepWithTag #'vlc \music
@@ -561,7 +561,7 @@ parts.  For example, the time signature and key signatures are almost
 always the same for all parts.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 global = {
    \key c \major
    \time 4/4
@@ -642,7 +642,7 @@ to the vocal notes (say, tenorMusic), then the changes will also
 apply to the piano reduction.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 global = {
    \key c \major
    \time 4/4
@@ -735,7 +735,7 @@ Here all the lyrics lines are placed using @code{alignAboveContext}
 and @code{alignBelowContext}.
 
 @lilypond[quote,verbatim,ragged-right]
-\version "2.11.15"
+\version "2.11.23"
 global = {
   \key c \major
   \time 4/4
@@ -859,7 +859,7 @@ notes.  As a compromise, bar lines are often printed between the
 staves rather than on the staves.
 
 @lilypond[quote,verbatim,line-width=11.0\cm]
-\version "2.11.15"
+\version "2.11.23"
 
 global = {
   \set Score.skipBars = ##t
@@ -1099,7 +1099,7 @@ quarter noteheads, and special marks, indicating rests of different length.
 
 @lilypond[quote,verbatim,ragged-right]
 \include "gregorian-init.ly"
-\version "2.11.15"
+\version "2.11.23"
 
 chant = \relative c' {
   \set Score.timing = ##f
@@ -1159,7 +1159,7 @@ is within a @code{\transpose} section.
 @c The `line-width' argument is for the \header.
 
 @lilypond[quote,verbatim,ragged-right,line-width]
-\version "2.11.15"
+\version "2.11.23"
 \header {
   title = "Song"
   subtitle = "(tune)"
@@ -1435,7 +1435,7 @@ violin concerto as TchaikovskyPI, whereas perhaps you wish to print
 
 @ The `line-width' is for \header.
 @li lypond[quote,verbatim,ragged-right,line-width]
-\version "2.11.15"
+\version "2.11.23"
 \header {
   dedication = "dedication"
   title = "Title"
diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 4752bf489e..049407ebcb 100644
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -1284,7 +1284,7 @@ The @code{\version} statement marks for which version of LilyPond the file
 was written.  To mark a file for version 2.10.1, place
 
 @example
-\version "2.11.15"
+\version "2.11.23"
 @end example
 
 @noindent
@@ -1305,7 +1305,7 @@ music expression; the @code{\header} block is usually placed underneath
 the @ref{Version number}.
 
 @example
-\version "2.11.15"
+\version "2.11.23"
 \header @{
   title = "Symphony"
   composer = "Me"
diff --git a/Documentation/user/working.itely b/Documentation/user/working.itely
index ad0aa964fd..1cc6ea71ef 100644
--- a/Documentation/user/working.itely
+++ b/Documentation/user/working.itely
@@ -70,7 +70,7 @@ problems:
 
 @itemize @bullet
 @item @strong{Include @code{\version} numbers in every file}.  Note that all
-templates contain a @code{\version "2.11.15"} string.  We
+templates contain a @code{\version "2.11.23"} string.  We
 highly recommend that you always include the @code{\version}, no matter
 how small your file is.  Speaking from personal experience, it's
 quite frustrating to try to remember which version of LilyPond you were
@@ -537,7 +537,7 @@ file with @code{\include "../global.ly"}, which contains
 
 @example
 %%%   global.ly
-\version "2.11.15"
+\version "2.11.23"
 #(ly:set-option 'point-and-click #f)
 \include "../init/init-defs.ly"
 \include "../init/init-layout.ly"
-- 
2.39.5