Left: | ||
Right: |
OLD | NEW |
---|---|
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 316 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
327 | 327 |
328 Notation Reference: | 328 Notation Reference: |
329 @ruser{Predefined type predicates}. | 329 @ruser{Predefined type predicates}. |
330 | 330 |
331 Installed Files: | 331 Installed Files: |
332 @file{lily/music-scheme.cc}, | 332 @file{lily/music-scheme.cc}, |
333 @file{scm/c++.scm}, | 333 @file{scm/c++.scm}, |
334 @file{scm/lily.scm}. | 334 @file{scm/lily.scm}. |
335 | 335 |
336 | 336 |
337 @node Music function usage | 337 @node Music function usage |
dak
2014/06/23 07:46:23
I think I'm responsible for most of this section.
pkx166h
2014/06/25 21:16:28
Done.
| |
338 @subsection Music function usage | 338 @subsection Music function usage |
339 Music functions may currently be used in several places. Depending on | 339 The result a music function returns must be music which is compatible |
340 where they are used, restrictions apply in order to be able to parse | 340 with the context in which it is called. In order to parse a music |
341 them unambiguously. The result a music function returns must be | 341 function unambiguously, the following context-dependent restrictions |
342 compatible with the context in which it is called. | 342 apply: |
343 | 343 |
344 @itemize | 344 @itemize |
345 @item | 345 @item |
346 At top level in a music expression. No restriction apply here. | 346 At the top level in a music expression. No restrictions apply here. |
dak
2014/06/23 07:46:23
Well, not your fault, but at top level LilyPond do
pkx166h
2014/06/25 21:16:28
Done.
| |
347 | 347 |
348 @item | 348 @item |
349 As a post-event, explicitly started with a direction indicator (one of | 349 As a post-event, explicitly started with a direction indicator (one of |
dak
2014/06/23 07:46:23
When a music function (as opposed to an event func
pkx166h
2014/06/25 21:16:28
Done.
| |
350 @code{-}, @code{^}, @w{and @code{_}}). | 350 @code{-}, @code{^}, @w{and @code{_}}). |
351 | 351 |
352 In this case, you can't use an @emph{open} music expression as the last | 352 In this case, you can't use an @emph{open} music expression as the last |
dak
2014/06/23 07:46:23
This paragraph can be stricken as of issue 3723, v
pkx166h
2014/06/25 21:16:28
Done.
| |
353 argument, one that would end with a music expression able to accept | 353 argument, i.e. one that would end with a music expression able to accept |
354 additional postevents. | 354 additional postevents. |
355 | 355 |
356 @item | 356 @item |
357 As a chord constituent. The returned expression must be of | 357 As a chord constituent. The returned expression must be of a |
358 @code{rhythmic-event} type, most likely a @code{NoteEvent}. | 358 @code{rhythmic-event} type, most likely a @code{NoteEvent}. |
359 @end itemize | 359 @end itemize |
360 | 360 |
361 @noindent | 361 @noindent |
362 The special rules for trailing arguments make it possible to write | 362 The special rules for trailing arguments make it possible to write |
dak
2014/06/23 07:46:24
"The special rules for trailing arguments" is nons
pkx166h
2014/06/25 21:16:28
Done.
| |
363 polymorphic functions like @code{\tweak} that can be applied to | 363 polymorphic functions, like @code{\tweak}, that can be applied to |
364 different constructs. | 364 different constructs. |
365 | 365 |
366 @node Simple substitution functions | 366 @node Simple substitution functions |
367 @subsection Simple substitution functions | 367 @subsection Simple substitution functions |
368 | 368 |
369 Simple substitution functions are music functions whose output | 369 Simple substitution functions are music functions whose output |
370 music expression is written in LilyPond format and contains | 370 music expression is written in LilyPond format and contains |
371 function arguments in the output expression. They are described | 371 function arguments in the output expression. They are described |
372 in @ruser{Substitution function examples}. | 372 in @ruser{Substitution function examples}. |
373 | 373 |
(...skipping 1077 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
1451 @end itemize | 1451 @end itemize |
1452 | 1452 |
1453 @node LilyPond Scheme interfaces | 1453 @node LilyPond Scheme interfaces |
1454 @chapter LilyPond Scheme interfaces | 1454 @chapter LilyPond Scheme interfaces |
1455 | 1455 |
1456 This chapter covers the various tools provided by LilyPond to help | 1456 This chapter covers the various tools provided by LilyPond to help |
1457 Scheme programmers get information into and out of the music streams. | 1457 Scheme programmers get information into and out of the music streams. |
1458 | 1458 |
1459 TODO -- figure out what goes in here and how to organize it | 1459 TODO -- figure out what goes in here and how to organize it |
1460 | 1460 |
OLD | NEW |