From: jlowe Date: Mon, 17 Jan 2011 17:08:02 +0000 (+0000) Subject: Doc: Perform fold on itely files for linelength X-Git-Tag: release/2.13.47-1~47 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=42d5df998cb69b0c66f967b3b5043e83bc504be6;hp=85c0ce205e1a9b5fad4ac79d02292ac1231db532;p=lilypond.git Doc: Perform fold on itely files for linelength As per CG for max linelength in itely files ran fold -s -w 72 *.itely Rechecked for any 'silly' results including broken @ref{} lines. Also checked the @seealso and added missing ones where appropriate --- diff --git a/Documentation/notation/text.itely b/Documentation/notation/text.itely index 159db9703d..6841e44dcb 100644 --- a/Documentation/notation/text.itely +++ b/Documentation/notation/text.itely @@ -63,19 +63,18 @@ in @ref{Direction and placement}. a8^"pizz." g f e a4-"scherz." f @end lilypond -This syntax is actually a shorthand; more complex text -formatting may be added to a note by explicitly using a -@code{\markup} block, as described in @ref{Formatting text}. +This syntax is actually a shorthand; more complex text formatting may be +added to a note by explicitly using a @code{\markup} block, as described +in @ref{Formatting text}. @lilypond[quote,verbatim,relative=2] a8^\markup { \italic pizz. } g f e a4_\markup { \tiny scherz. \bold molto } f @end lilypond -By default, text indications do not influence the note spacing. -However, their widths can be taken into account: -in the following example, the first text string does not affect -spacing, whereas the second one does. +By default, text indications do not influence the note spacing. However, +their widths can be taken into account: in the following example, the +first text string does not affect spacing, whereas the second one does. @lilypond[quote,verbatim,relative=2] a8^"pizz." g f e @@ -106,7 +105,8 @@ Learning Manual: Notation Reference: @ref{Formatting text}, -@ref{Direction and placement}. +@ref{Direction and placement}, +@ref{Articulations and ornamentations}. Snippets: @rlsr{Text}. @@ -122,7 +122,6 @@ Internals Reference: @knownissues - Checking to make sure that text scripts and lyrics are within the margins is a relatively large computational task. To speed up processing, LilyPond does not perform such calculations by @@ -197,7 +196,8 @@ LilyPond is only able to handle one text spanner per voice. @seealso Notation Reference: @ref{Line styles}, -@ref{Dynamics}. +@ref{Dynamics}, +@ref{Formatting text}. Snippets: @rlsr{Text}, @@ -224,8 +224,8 @@ Internals Reference: @funindex \markup @funindex markup -Various text elements may be added to a score using -the syntax described in @ref{Rehearsal marks}: +Various text elements may be added to a score using the syntax described +in @ref{Rehearsal marks}: @c \mark needs to be placed on a separate line (it's not @c attached to an object like \markup is). -vv @@ -259,10 +259,11 @@ or fermata, by specifying the appropriate symbol name as explained in @end lilypond @noindent -Such objects are only typeset above the top staff of the score; depending on -whether they are specified at the end or the middle of a bar, they -can be placed above the bar line or between notes. When specified at a -line break, the mark will be printed at the beginning of the next line. +Such objects are only typeset above the top staff of the score; +depending on whether they are specified at the end or the middle of a +bar, they can be placed above the bar line or between notes. When +specified at a line break, the mark will be printed at the beginning of +the next line. @lilypond[quote,verbatim,relative=2] \mark "Allegro" @@ -495,7 +496,6 @@ Installed Files: @knownissues - Syntax errors for markup mode can be confusing. @@ -1122,7 +1122,8 @@ An exhaustive list of graphics-specific commands can be found in @seealso Notation Reference: @ref{Graphic}, -@ref{Editorial annotations}. +@ref{Editorial annotations}, +@ref{Align}. Snippets: @rlsr{Text}. @@ -1455,6 +1456,7 @@ possible to use other fonts, as explained in the following sections: Notation Reference: @ref{The Feta font}, @ref{Music notation inside markup}, +@ref{Rotating objects}, @ref{Selecting font and font size}, @ref{Font}. diff --git a/Documentation/notation/vocal.itely b/Documentation/notation/vocal.itely index b09a7cd1a5..d54bb08122 100644 --- a/Documentation/notation/vocal.itely +++ b/Documentation/notation/vocal.itely @@ -205,7 +205,8 @@ Notation Reference: @ref{Automatic syllable durations}, @ref{Fonts}, @ref{Input modes}, -@ref{Manual syllable durations}. +@ref{Manual syllable durations}, +@ref{Text encoding}. Internals Reference: @rinternals{LyricText}. @@ -322,6 +323,14 @@ specifying an associated voice, if one exists. For details, see Learning Manual: @rlearning{Aligning lyrics to a melody}. +Notation Reference: +@ref{Contexts explained}, +@ref{Automatic syllable durations}. +@ref{Stanzas}, +@ref{Manual syllable durations}, +@ref{Dialogue over music}, +@ref{Manual syllable durations}. + Internals Reference: @rinternals{Lyrics}. @@ -487,7 +496,8 @@ Here is an example demonstrating its use: @seealso Notation Reference: @ref{Extenders and hyphens}, -@ref{Keeping contexts alive}. +@ref{Keeping contexts alive}, +@ref{Placing lyrics vertically}. @node Manual syllable durations @unnumberedsubsubsec Manual syllable durations @@ -1116,9 +1126,9 @@ To make this change for all lyrics in the score, set the property in the @c TODO: move to LSR -vv -Checking to make sure that text scripts and lyrics are within the margins is -a relatively large computational task. To speed up processing, LilyPond does -not perform such calculations by default; to enable it, use +Checking to make sure that text scripts and lyrics are within the +margins is a relatively large computational task. To speed up processing, +LilyPond does not perform such calculations by default; to enable it, use @example \override Score.PaperColumn #'keep-inside-line = ##t @@ -1516,6 +1526,10 @@ alternative sections these must be inserted manually. } @end lilypond +@seealso +Notation Reference: +@ref{Keeping contexts alive}, +@ref{Repeats}. @node Divisi lyrics @@ -1660,9 +1674,9 @@ stanzaOneThree = { Stanzas differing in loudness may be indicated by putting a dynamics mark before each stanza. In LilyPond, everything coming in -front of a stanza goes into the @code{StanzaNumber} object; dynamics marks -are no different. For technical reasons, you have to set the stanza -outside @code{\lyricmode}: +front of a stanza goes into the @code{StanzaNumber} object; dynamics +marks are no different. For technical reasons, you have to set the +stanza outside @code{\lyricmode}: @lilypond[quote,ragged-right,verbatim] text = { @@ -1936,10 +1950,11 @@ text = \lyricmode { It has two lines. } -\score{ << +\score { + << \new Voice = "one" { \melody } \new Lyrics \lyricsto "one" \text - >> + >> \layout { } } @@ -2037,8 +2052,7 @@ For entering stanzas, see @ref{Stanzas}. @item Songs are frequently printed with the chording indicated by chord -names above the staves. This is described in -@ref{Displaying chords}. +names above the staves. This is described in @ref{Displaying chords}. @item To print fret diagrams of the chords for guitar accompaniment or @@ -2608,8 +2622,8 @@ declaring separate @code{CueVoice} contexts and using @cindex parlato @cindex Sprechgesang -Such effects as @q{parlato} or @q{Sprechgesang} require performers to speak -without pitch but still with rhythm; these are notated by cross +Such effects as @q{parlato} or @q{Sprechgesang} require performers to +speak without pitch but still with rhythm; these are notated by cross note heads, as demonstrated in @ref{Special note heads}. @c TODO add "marking-notes-on-spoken-parts" snippet -vv