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

Side by Side Diff: Documentation/learning/fundamental.itely

Issue 343060043: Clarify notation for slurs and beams
Patch Set: Created 5 years, 11 months 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/common-notation.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 22 matching lines...) Expand all
33 users a lot of flexibility to structure their files however they 33 users a lot of flexibility to structure their files however they
34 wish. But this flexibility can make things confusing for new 34 wish. But this flexibility can make things confusing for new
35 users. This section will explain some of this structure, but may 35 users. This section will explain some of this structure, but may
36 gloss over some details in favor of simplicity. For a complete 36 gloss over some details in favor of simplicity. For a complete
37 description of the input format, see @ruser{File structure}. 37 description of the input format, see @ruser{File structure}.
38 38
39 @menu 39 @menu
40 * Introduction to the LilyPond file structure:: 40 * Introduction to the LilyPond file structure::
41 * Score is a (single) compound musical expression:: 41 * Score is a (single) compound musical expression::
42 * Nesting music expressions:: 42 * Nesting music expressions::
43 * Structure of a note entry::
43 * On the un-nestedness of brackets and ties:: 44 * On the un-nestedness of brackets and ties::
44 @end menu 45 @end menu
45 46
46 @node Introduction to the LilyPond file structure 47 @node Introduction to the LilyPond file structure
47 @subsection Introduction to the LilyPond file structure 48 @subsection Introduction to the LilyPond file structure
48 49
49 @cindex input format 50 @cindex input format
50 @cindex file structure 51 @cindex file structure
51 52
52 A basic example of a LilyPond input file is 53 A basic example of a LilyPond input file is
(...skipping 397 matching lines...) Expand 10 before | Expand all | Expand 10 after
450 position which is below. 451 position which is below.
451 452
452 453
453 @seealso 454 @seealso
454 Ossia are often written without clef and without 455 Ossia are often written without clef and without
455 time signature and are usually in a smaller font. 456 time signature and are usually in a smaller font.
456 These require further commands which 457 These require further commands which
457 have not yet been introduced. See @ref{Size of objects}, 458 have not yet been introduced. See @ref{Size of objects},
458 and @ruser{Ossia staves}. 459 and @ruser{Ossia staves}.
459 460
461 @node Structure of a note entry
462 @subsection Structure of a note entry
463
464 A note entry in LilyPond consists of a pitch, followed by a duration,
465 optionally followed by one or more post-events. Post-events add
466 things such as articulations, fingerings, string numbers, slurs, ties
467 and explanatory text.
468
469 The pitch may be explicitly defined using the current LilyPond input
470 language as described in @ruser{Note names in other languages}. The
471 pitch may be omitted. If the pitch is omitted, the pitch of a current
472 note will be the same as the pitch of the previous note in the input
473 file, see @ruser{Durations}.
474
475 The duration includes a number and optionally one or more dots. If a
476 duration is not explicitly defined, the duration of a current note will
477 be the same as the duration of the previous note, chord, rest, or spacer
478 rest, see @ruser{Durations}.
479
480 Post-events follow the note to which they are attached. Suppose we
481 want to have an eighth note c' with a fingering of 1, a tenuto
482 articulation, a slur beginning with the note, a tie beginning with
483 the note, and a text annotation. This can be accomplished as
484 shown.
485
486 @lilypond[verbatim,quote]
487 \absolute {c'8-1--(~^\markup{"text annotationi"} c' d')}
Be-3 2018/04/30 11:37:09 Shouldn't it be "text annotation"?
488 @end lilypond
Trevor Daniels 2018/04/30 12:08:19 I'd prefer \relative or nothing in this example. \
489
490 @seealso @ruser{Pitches},
491 @ruser{Rhythms},
492 @ruser{Expressive marks},
Trevor Daniels 2018/04/30 12:08:20 Might be good to point to the relevant sections in
460 493
461 @node On the un-nestedness of brackets and ties 494 @node On the un-nestedness of brackets and ties
462 @subsection On the un-nestedness of brackets and ties 495 @subsection On the un-nestedness of brackets and ties
463 496
464 @cindex brackets, nesting 497 @cindex brackets, nesting
465 @cindex bracket types 498 @cindex bracket types
466 @cindex brackets, enclosing vs. marking 499 @cindex brackets, enclosing vs. marking
467 500
468 You have already met a number of different types of bracket and 501 You have already met a number of different types of bracket and
469 bracket-like constructs in writing the input file to LilyPond. 502 bracket-like constructs in writing the input file to LilyPond.
(...skipping 2803 matching lines...) Expand 10 before | Expand all | Expand 10 after
3273 @seealso 3306 @seealso
3274 Learning Manual: 3307 Learning Manual:
3275 @ref{Organizing pieces with variables}. 3308 @ref{Organizing pieces with variables}.
3276 3309
3277 Notation Reference: 3310 Notation Reference:
3278 @ruser{Transpose}, 3311 @ruser{Transpose},
3279 @ruser{Writing parts}, 3312 @ruser{Writing parts},
3280 @ruser{Full measure rests}, 3313 @ruser{Full measure rests},
3281 @ruser{Including LilyPond files}. 3314 @ruser{Including LilyPond files}.
3282 3315
OLDNEW
« no previous file with comments | « Documentation/learning/common-notation.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