Left: | ||
Right: |
LEFT | RIGHT |
---|---|
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 444 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
455 Ossia are often written without clef and without | 455 Ossia are often written without clef and without |
456 time signature and are usually in a smaller font. | 456 time signature and are usually in a smaller font. |
457 These require further commands which | 457 These require further commands which |
458 have not yet been introduced. See @ref{Size of objects}, | 458 have not yet been introduced. See @ref{Size of objects}, |
459 and @ruser{Ossia staves}. | 459 and @ruser{Ossia staves}. |
460 | 460 |
461 @node Structure of a note entry | 461 @node Structure of a note entry |
462 @subsection Structure of a note entry | 462 @subsection Structure of a note entry |
463 | 463 |
464 A note entry in LilyPond consists of a pitch, followed by a duration, | 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 | 465 optionally followed by one or more @q{post-events}. LilyPond |
466 things such as articulations, fingerings, string numbers, slurs, ties | 466 post-events add things such as articulations, fingerings, string numbers, |
467 and explanatory text. | 467 slurs, ties and explanatory text. |
468 | 468 |
469 The pitch may be explicitly defined using the current LilyPond input | 469 The pitch may be explicitly defined using the current LilyPond input |
470 language as described in @ruser{Note names in other languages}. The | 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 | 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 | 472 note will be the same as the pitch of the previous note in the input |
473 file, see @ruser{Durations}. Note that neither @code{r} nor @code{s} | 473 file, see @ruser{Durations}. Note that neither @code{r} nor @code{s} |
474 is a pitch. | 474 is a pitch. |
475 | 475 |
476 The duration includes a number and optionally one or more dots. If a | 476 The duration includes a number and optionally one or more dots. If a |
477 duration is not explicitly defined, the duration of a current note will | 477 duration is not explicitly defined, the duration of a current note will |
478 be the same as the duration of the previous note, chord, rest, or spacer | 478 be the same as the duration of the previous note, chord, rest, or spacer |
479 rest, see @ruser{Durations}. | 479 rest, see @ruser{Durations}. |
480 | 480 |
481 Post-events follow the note to which they are attached. Suppose we | 481 Post-events follow the note to which they are attached. Suppose we |
482 want to have an eighth note c' with a fingering of 1, a tenuto | 482 want to have an eighth note c' with a fingering of 1, a tenuto |
483 articulation, a slur beginning with the note, a tie beginning with | 483 articulation, a slur beginning with the note, a tie beginning with |
484 the note, and a text annotation. This can be accomplished as | 484 the note, and a text annotation. This can be accomplished as |
485 shown. | 485 shown. |
486 | 486 |
487 @lilypond[verbatim,quote] | 487 @lilypond[verbatim,quote] |
488 {c'8-1--(~^\markup{"text annotation"} c' d')} | 488 {c'8-1--(~^\markup{"text annotation"} c' d')} |
489 @end lilypond | 489 @end lilypond |
490 | 490 |
491 @seealso | 491 @seealso |
492 Learning Manual: | 492 Learning Manual: |
493 @rlearning{Ties and slurs}, | 493 @ref{Ties and slurs}, |
494 @rlearning{Articulations and dynamics}, | 494 @ref{Articulations and dynamics}, |
495 @rlearning{Adding text}. | 495 @ref{Adding text}. |
Trevor Daniels
2018/04/30 15:47:26
Not sure if it makes any difference but we usually
Carl
2018/04/30 15:51:16
Fundamentals is in a different source file than co
Trevor Daniels
2018/04/30 17:04:01
@ref definitely should work. It may be that the h
| |
496 | 496 |
497 Notation Reference: | 497 Notation Reference: |
498 @ruser{Pitches}, | 498 @ruser{Pitches}, |
499 @ruser{Rhythms}, | 499 @ruser{Rhythms}, |
500 @ruser{Expressive marks}. | 500 @ruser{Expressive marks}. |
501 | 501 |
502 @node On the un-nestedness of brackets and ties | 502 @node On the un-nestedness of brackets and ties |
503 @subsection On the un-nestedness of brackets and ties | 503 @subsection On the un-nestedness of brackets and ties |
504 | 504 |
505 @cindex brackets, nesting | 505 @cindex brackets, nesting |
(...skipping 2808 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
3314 @seealso | 3314 @seealso |
3315 Learning Manual: | 3315 Learning Manual: |
3316 @ref{Organizing pieces with variables}. | 3316 @ref{Organizing pieces with variables}. |
3317 | 3317 |
3318 Notation Reference: | 3318 Notation Reference: |
3319 @ruser{Transpose}, | 3319 @ruser{Transpose}, |
3320 @ruser{Writing parts}, | 3320 @ruser{Writing parts}, |
3321 @ruser{Full measure rests}, | 3321 @ruser{Full measure rests}, |
3322 @ruser{Including LilyPond files}. | 3322 @ruser{Including LilyPond files}. |
3323 | 3323 |
LEFT | RIGHT |