Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(1342)

Side by Side Diff: Documentation/notation/input.itely

Issue 579280043: Doc: Some miscellaneous suggestions from Peter Toye
Patch Set: Use singular form for index entries Created 4 years, 1 month ago
Left:
Right:
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
View unified diff | Download patch
« no previous file with comments | « Documentation/learning/tutorial.itely ('k') | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 @c -*- coding: utf-8; mode: texinfo; -*- 1 @c -*- coding: utf-8; mode: texinfo; -*-
2 2
3 @ignore 3 @ignore
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH 4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 5
6 When revising a translation, copy the HEAD committish of the 6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. For details, see the Contributors' 7 version that you are working on. For details, see the Contributors'
8 Guide, node Updating translation committishes.. 8 Guide, node Updating translation committishes..
9 @end ignore 9 @end ignore
10 10
(...skipping 436 matching lines...) Expand 10 before | Expand all | Expand 10 after
447 expressions, wherever they appear. 447 expressions, wherever they appear.
448 448
449 @cindex variables 449 @cindex variables
450 450
451 @item 451 @item
452 A variable, such as 452 A variable, such as
453 @example 453 @example
454 foo = @{ c4 d e d @} 454 foo = @{ c4 d e d @}
455 @end example 455 @end example
456 456
457 This can be used later on in the file by entering @code{\foo}. The 457 This can be used later on in the file by entering @code{\foo}.
458 name of a variable should have alphabetic characters only; no 458 The name of a variable should not contain (ASCII) numbers,
459 numbers, underscores or dashes. 459 multiple underscores, multiple dashes or space characters.
460 All other characters Unicode provides are allowed, for example
461 Latin, Greek, Chinese or Cyrillic. Non-adjacent single
462 underscores and dashes are allowed, too.
463 In other words, variable names like @code{HornIII} or
464 @code{αβγXII} work.
465
466 Any combination of characters is allowed if the variable name
467 is enclosed in double quotation marks. In this case backslashes
468 and double quotation marks need to be escaped with
469 backslashes (not that you actually should use them).
470 Examples: @code{"foo bar"}, @code{"a-b-c"}, @code{"Horn 3"}.
460 471
461 @end itemize 472 @end itemize
462 473
463 The following example shows three things that may be entered at 474 The following example shows three things that may be entered at
464 toplevel 475 toplevel
465 476
466 @example 477 @example
467 \layout @{ 478 \layout @{
468 % Don't justify the output 479 % Don't justify the output
469 ragged-right = ##t 480 ragged-right = ##t
(...skipping 386 matching lines...) Expand 10 before | Expand all | Expand 10 after
856 @ref{Custom layout for titles}, 867 @ref{Custom layout for titles},
857 @ref{File structure}. 868 @ref{File structure}.
858 869
859 Installed Files: 870 Installed Files:
860 @file{ly/titling-init.ly}. 871 @file{ly/titling-init.ly}.
861 872
862 873
863 @node Default layout of headers and footers 874 @node Default layout of headers and footers
864 @unnumberedsubsubsec Default layout of headers and footers 875 @unnumberedsubsubsec Default layout of headers and footers
865 876
877 @cindex page header
878 @cindex page footer
879 @cindex header, page
880 @cindex footer, page
881
866 @emph{Headers} and @emph{footers} are lines of text appearing at 882 @emph{Headers} and @emph{footers} are lines of text appearing at
867 the top and bottom of pages, separate from the main text of a book. 883 the top and bottom of pages, separate from the main text of a book.
868 They are controlled by the following @code{\paper} variables: 884 They are controlled by the following @code{\paper} variables:
869 885
870 @itemize 886 @itemize
871 @item @code{oddHeaderMarkup} 887 @item @code{oddHeaderMarkup}
872 @item @code{evenHeaderMarkup} 888 @item @code{evenHeaderMarkup}
873 @item @code{oddFooterMarkup} 889 @item @code{oddFooterMarkup}
874 @item @code{evenFooterMarkup} 890 @item @code{evenFooterMarkup}
875 @end itemize 891 @end itemize
(...skipping 1360 matching lines...) Expand 10 before | Expand all | Expand 10 after
2236 2252
2237 The arguments of the @code{\tag}, @code{\keepWithTag} and 2253 The arguments of the @code{\tag}, @code{\keepWithTag} and
2238 @code{\removeWithTag} commands should be a symbol or list of 2254 @code{\removeWithTag} commands should be a symbol or list of
2239 symbols (such as @code{#'score} or @code{#'(violinI violinII}), 2255 symbols (such as @code{#'score} or @code{#'(violinI violinII}),
2240 followed by a music expression. If @emph{and only if} the symbols 2256 followed by a music expression. If @emph{and only if} the symbols
2241 are valid LilyPond identifiers (alphabetic characters only, no 2257 are valid LilyPond identifiers (alphabetic characters only, no
2242 numbers, underscores, or dashes) which cannot be confused with notes, 2258 numbers, underscores, or dashes) which cannot be confused with notes,
2243 the @code{#'} may be omitted and, as a shorthand, a list of symbols 2259 the @code{#'} may be omitted and, as a shorthand, a list of symbols
2244 can use the dot separator: i.e., @code{\tag #'(violinI violinII)} can 2260 can use the dot separator: i.e., @code{\tag #'(violinI violinII)} can
2245 be written @code{\tag violinI.violinII}. The same applies to 2261 be written @code{\tag violinI.violinII}. The same applies to
2246 @code{\keepWithTag} and @code{\removeWithTag}. 2262 @code{\keepWithTag} and @code{\removeWithTag}. Tagging commands
2263 are music functions, thus they cannot be used to filter items that
2264 are not music expressions, such as @code{\book} or @code{\score} blocks.
2247 2265
2248 In the following example, we see two versions of a piece of music, 2266 In the following example, we see two versions of a piece of music,
2249 one showing trills with the usual notation, and one with trills 2267 one showing trills with the usual notation, and one with trills
2250 explicitly expanded: 2268 explicitly expanded:
2251 2269
2252 @lilypond[verbatim,quote] 2270 @lilypond[verbatim,quote]
2253 music = \relative { 2271 music = \relative {
2254 g'8. c32 d 2272 g'8. c32 d
2255 \tag #'trills { d8.\trill } 2273 \tag #'trills { d8.\trill }
2256 \tag #'expand { \repeat unfold 3 { e32 d } } 2274 \tag #'expand { \repeat unfold 3 { e32 d } }
(...skipping 1714 matching lines...) Expand 10 before | Expand all | Expand 10 after
3971 3989
3972 3990
3973 @knownissues 3991 @knownissues
3974 3992
3975 Not all lilypond music events are supported by 3993 Not all lilypond music events are supported by
3976 @file{event-listener.ly}. It is intended to be a well-crafted 3994 @file{event-listener.ly}. It is intended to be a well-crafted
3977 @qq{proof of concept}. If some events that you want to see are 3995 @qq{proof of concept}. If some events that you want to see are
3978 not included, copy @file{event-listener.ly} into your lilypond 3996 not included, copy @file{event-listener.ly} into your lilypond
3979 directory and modify the file so that it outputs the information 3997 directory and modify the file so that it outputs the information
3980 you want. 3998 you want.
OLDNEW
« no previous file with comments | « Documentation/learning/tutorial.itely ('k') | no next file » | no next file with comments »

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b