From f956f2271edf2d501625c89624321c20b75695d1 Mon Sep 17 00:00:00 2001 From: John Mandereau Date: Tue, 13 Feb 2007 17:56:45 +0100 Subject: [PATCH] Convert-ly the user manual This was not necessary, but I had some doubt. --- Documentation/fr/user/tutorial.itely | 4 +-- Documentation/fr/user/working.itely | 2 +- Documentation/user/README.txt | 2 +- Documentation/user/non-music.itely | 2 +- Documentation/user/putting.itely | 8 ++--- Documentation/user/spacing.itely | 2 +- Documentation/user/templates.itely | 44 ++++++++++++++-------------- Documentation/user/tutorial.itely | 4 +-- Documentation/user/working.itely | 4 +-- 9 files changed, 36 insertions(+), 36 deletions(-) diff --git a/Documentation/fr/user/tutorial.itely b/Documentation/fr/user/tutorial.itely index 7b9d9c443a..47d957ca09 100644 --- a/Documentation/fr/user/tutorial.itely +++ b/Documentation/fr/user/tutorial.itely @@ -1399,7 +1399,7 @@ LilyPond pour laquelle le fichier a été écrit. Pour donner à un fichier la version 2.10.0, ajoutez @example -\version "2.10.1" +\version "2.10.10" @end example @noindent @@ -1422,7 +1422,7 @@ principales. Le bloc @code{\header} est habituellement placé en début de fichier. @example -\version "2.10.1" +\version "2.10.10" \header @{ title = "Symphonie" composer = "Moi" diff --git a/Documentation/fr/user/working.itely b/Documentation/fr/user/working.itely index 3fd4bd3f42..827184883b 100644 --- a/Documentation/fr/user/working.itely +++ b/Documentation/fr/user/working.itely @@ -539,7 +539,7 @@ musique par @code{\include "../global.ly"} qui contient : @example %%% global.ly -\version "2.9.13" +\version "2.10.10" #(ly:set-option 'point-and-click #f) \include "../init/init-defs.ly" \include "../init/init-mise-en-page.ly" diff --git a/Documentation/user/README.txt b/Documentation/user/README.txt index 0b07678e3b..3d44c6fa2c 100644 --- a/Documentation/user/README.txt +++ b/Documentation/user/README.txt @@ -1,7 +1,7 @@ Info for Documentation ---------------------- -Current version of the manual: 2.9.13 +Current version of the manual: 2.10.17 *** Please update this whenever you run convert-ly on the docs. convert-ly --from=... --to=... --no-version *.itely diff --git a/Documentation/user/non-music.itely b/Documentation/user/non-music.itely index 1401eeb5d5..a6c4e42d59 100644 --- a/Documentation/user/non-music.itely +++ b/Documentation/user/non-music.itely @@ -49,7 +49,7 @@ these files end with @q{@samp{.ly}}. A basic example of a lilypond input file is @example -\version "2.9.13" +\version "2.10.10" \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 f5e365a29a..efbae5fd25 100644 --- a/Documentation/user/putting.itely +++ b/Documentation/user/putting.itely @@ -35,7 +35,7 @@ cello. In this case, we would start with @qq{Notes and lyrics} (for the soprano part). @example -\version "2.9.13" +\version "2.10.10" 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 @qq{Notes only} example: @example -\version "2.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" sopranoMusic = \relative c' { \clef treble \key c \major diff --git a/Documentation/user/spacing.itely b/Documentation/user/spacing.itely index d98dbc2110..8d105ebed1 100644 --- a/Documentation/user/spacing.itely +++ b/Documentation/user/spacing.itely @@ -117,7 +117,7 @@ The default layout responds to the following settings in the @item first-page-number The value of the page number of the first page. Default is@tie{}1. -@funindex printfirst-page-number +@funindex print-first-page-number @item print-first-page-number If set to true, will print the page number in the first page. Default is false. diff --git a/Documentation/user/templates.itely b/Documentation/user/templates.itely index 39c983fcbb..664416f5c4 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.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" 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.9.13" +\version "2.10.10" upper = \relative c'' { \clef treble \key c \major @@ -399,7 +399,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.9.13" +\version "2.10.10" global= { \time 4/4 @@ -459,7 +459,7 @@ contains all the music definitions. The other files -- @code{score.ly}, @verbatim %%%%% piece.ly -\version "2.9.13" +\version "2.10.10" global= { \time 4/4 @@ -505,7 +505,7 @@ music = { %%%%% score.ly -\version "2.9.13" +\version "2.10.10" \include "piece.ly" #(set-global-staff-size 14) \score { @@ -516,7 +516,7 @@ music = { %%%%% vn1.ly -\version "2.9.13" +\version "2.10.10" \include "piece.ly" \score { \keepWithTag #'vn1 \music @@ -525,7 +525,7 @@ music = { %%%%% vn2.ly -\version "2.9.13" +\version "2.10.10" \include "piece.ly" \score { \keepWithTag #'vn2 \music @@ -534,7 +534,7 @@ music = { %%%%% vla.ly -\version "2.9.13" +\version "2.10.10" \include "piece.ly" \score { \keepWithTag #'vla \music @@ -543,7 +543,7 @@ music = { %%%%% vlc.ly -\version "2.9.13" +\version "2.10.10" \include "piece.ly" \score { \keepWithTag #'vlc \music @@ -563,7 +563,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.9.13" +\version "2.10.10" global = { \key c \major \time 4/4 @@ -644,7 +644,7 @@ to the vocal notes (say, tenorMusic), then the changes will also apply to the piano reduction. @lilypond[quote,verbatim,ragged-right] -\version "2.9.13" +\version "2.10.10" global = { \key c \major \time 4/4 @@ -737,7 +737,7 @@ Here all the lyrics lines are placed using @code{alignAboveContext} and @code{alignBelowContext}. @lilypond[quote,verbatim,ragged-right] -\version "2.10.0" +\version "2.10.10" global = { \key c \major \time 4/4 @@ -861,7 +861,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.9.13" +\version "2.10.10" global = { \set Score.skipBars = ##t @@ -1101,7 +1101,7 @@ quarter noteheads, and special marks, indicating rests of different length. @lilypond[quote,verbatim,ragged-right] \include "gregorian-init.ly" -\version "2.9.13" +\version "2.10.10" chant = \relative c' { \set Score.timing = ##f @@ -1161,7 +1161,7 @@ is within a @code{\transpose} section. @c The @q{line-width} argument is for the \header. @lilypond[quote,verbatim,ragged-right,line-width] -\version "2.9.13" +\version "2.10.10" \header { title = "Song" subtitle = "(tune)" @@ -1437,7 +1437,7 @@ violin concerto as TchaikovskyPI, whereas perhaps you wish to print @ The @q{line-width} is for \header. @li lypond[quote,verbatim,ragged-right,line-width] -\version "2.9.13" +\version "2.10.10" \header { dedication = "dedication" title = "Title" diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 93a5db0ec0..6ee13762ca 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -1294,7 +1294,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.10.1" +\version "2.10.10" @end example @noindent @@ -1315,7 +1315,7 @@ music expression; the @code{\header} block is usually placed underneath the @ref{Version number}. @example -\version "2.10.1" +\version "2.10.10" \header @{ title = "Symphony" composer = "Me" diff --git a/Documentation/user/working.itely b/Documentation/user/working.itely index 25e21993a5..b44f23d850 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.9.13"} string. We +templates contain a @code{\version "2.10.10"} 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.9.13" +\version "2.10.10" #(ly:set-option 'point-and-click #f) \include "../init/init-defs.ly" \include "../init/init-layout.ly" -- 2.39.5