kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/print/lilypond/PLIST

365 lines
18 KiB
Text
Raw Normal View History

Update to 2.18.0: New features in 2.18 since 2.16 ******************************* * There is now a new context type called `NullVoice' which, while not appearing in the printed output, can be used to align lyrics. This can be particularly convenient when used in parallel with a `\partcombine' construct. * Several articulations can be put into a single variable or returned from an event function. * The baseline of score markups is now taken from the reference point (usually the middle of the staff) of the first bottom system rather than the top of the bounding rectangle. * LilyPond no longer automatically infers a `\defaultchild' context in a context definition with `\accepts' clauses. Any context definition without an explicit or inherited `\defaultchild' definition counts as a `Bottom' context and will be eligible for rhythmic events and overrides without causing the implicit creation of other contexts. Be sure to specify a `\defaultchild' for non-`Bottom' contexts when defining them from scratch. * There is now extensive support for both discant and bass accordion register symbols in the `scm accreg' module. * New commands `markLengthOn' and `markLengthOff' control the allowance of horizontal space for tempo and rehearsal marks. * Rehearsal marks at the beginning of a line are now placed to the right of the clef and key signature by default. As in previous versions, the `break-alignable-interface' controls the behavior. * Decimal numbers can now be written directly in music, without a hash sign. Together with the previous change in the way object properties are specified, the code to change the length of stems has changed from this: \override Stem #'length = #5.6 e' f' g' a' to this: \override Stem.length = 5.6 e' f' g' a' One has to write a digit on both sides of the dot - values like `4.' or `-.3' are not allowed. Decimal fractions are also not accepted in `\chordmode'. * A number of shorthands like `(', `)', `|', `[', `]', `~', `\(', `\)' and others can now freely be redefined like normal commands. * The articulation shorthand for `\staccatissimo' has been renamed from `-|' to `-!'. * Tempo change ranges are now written as `\tempo 4 = 60 - 68' rather than `\tempo 4 = 60 ~ 68'. * Grob `OctavateEight' was renamed to `ClefModifier'. Related context properties were renamed from `xxxOctavationyyy' to `xxxTranspositionyyy'. * There is a new `\absolute' command explicitly marking music as being entered in absolute pitch. While this has been the default previously, an explicit `\absolute' also prevents reinterpretation when the passage is placed inside of `\relative'. * When `\relative' is used without an explicit reference pitch, the reference pitch now is the middle of the first octave, making the first entered pitch indistinguishable from absolute pitch. Previously, omitting the reference pitch would have lead to a default of `c''. Since that choice was somewhat arbitrary, recommended usage was to always specify the reference pitch. * A new command `\single' can be used for converting a property override into a tweak to be applied on a single music expression. * Two ways of letting graphical objects not appear in the output are overriding its `transparent' property with `#t' (retaining the original spacing) or overriding its `stencil' property with `#f' (not using any space at all). Those two operations now have the shorthands `\hide' and `\omit', respectively. * A new command `\temporary' can be applied to overrides in order to not have them replace previous property settings. If a `\revert' is applied to the same property subsequently, the previous setting reappears. This is mainly useful for writing music functions that need to have some property changed just for the duration of the function. * `\tag', `\removeWithTag', and `\keepWithTag' can now accept a list of symbols rather than just a single symbol for marking, removing, and keeping music with any of multiple tags. This is particularly important for `\keepWithTag' since one cannot achieve the same effect by using multiple consecutive `\keepWithTag' commands. * The `-d old-relative' option has been removed. Not actually accessible from the command line any more, its remaining use was for interpretating `\relative' in LilyPond files converted automatically from version 1.8 or older. It is unclear how much of this was actually still operative. * The meaning of `instrumentTransposition' has been reversed. After \set instrumentTransposition = #{ b #} a written `c'' now sounds like `b'. Previously, this would have been the other way round. This and the following change should make dealing with transposing instruments more straightforward. * The music generated by `\set' and `\override' commands is no longer affected by `\transpose'. The main consequence is that `\transpose' will transpose audible/concert pitch and printed pitch by the same amount even when the transposed music contains `\transposition'. Previously, \transpose c' f' \transposition bes' was equivalent to `\transposition f''. Now it stays equivalent to `\transposition bes''. * When checking for collisions, LilyPond no longer treats objects as rectangles. Instead, the actual shape of objects is approximated using an integral-like approach. This generally results in more even and snug positioning of objects and systems. Affected objects include `Accidentals', `Beams', `Clefs', `Dynamics', `FiguredBass', `Flags', `Glissandos', `Lyrics', `MetronomeMarks', `OttavaBrackets', `Pedals', `RehearsalMarks', `Rests', `Scripts', `TextScripts', `Ties', `Tuplets' and `VoltaBrackets'. * Tuplets are now created with the `\tuplet' command, which takes a fraction `T/N' to specify that T notes are played in the time usually allowed for N. One `\tuplet' command can create several tuplet groups if their duration is typed after the fraction. The `\times' command with its inverted fraction order `N/T' is still available. * Introducing two new markup-commands; `\draw-dashed-line' and `\draw-dotted-line'. The dashed-line extends to the whole length given by DEST, if `full-length' is set to `#t' (this is the default) without any space at the beginning or end. `off' will then be altered to fit. To insist on the given (or default) values of `on', `off' use `\override #'(full-length . #f)'. Manual settings for `on', `off' and `phase' are possible. The dotted-line always extends to the whole length given by DEST, without any space at the beginning or end. Manual settings for `off' are possible to get larger or smaller space between the dots. The given (or default) value of `off' will be altered to fit the line-length. * Starting with version 2.17.10, error messages or the `textedit' URI used for point-and-click functionality specify column numbers starting with 1 rather than 0. The byte offset (also part of `textedit' URIs) still starts at 0. * The `\clef' command supports optional transposition. * The LilyPond syntax of dot-separated words `Voice.Accidental' has been made interchangeable with `#'(Voice Accidental)', a Scheme list of symbols. * Grob and grob property path no longer need to be specified as two separate arguments to commands like `\override' and `\revert', allowing for the syntax \override Voice.TextSpanner.bound-details.left.text = "rit." Since complementary music functions like `\overrideProperty' cannot support forms with and without separating space at the same time, using a single dotted path is now the preferred form. Specifying grob path and grob property path separately, currently still supported with `\override' and `\revert' for compatibility reasons, is deprecated. * Due to words now being accepted as symbol function arguments, the interfaces of `\accidentalStyle', `\alterBroken', `\footnote' and `\tweak' had to be redesigned where optional symbol arguments were involved. Please check the respective music function documentation for details. * Several commands now accept symbol lists (conveniently entered as dot-separated words) for various kinds of arguments. These include `\accidentalStyle', `\alterBroken', `\footnote', `\hide', `\omit', `\overrideProperty', `\shape', and `\tweak'. * The bar line user interface has changed. Bar glyphs now resemble the appearance of the bar line, so a left repeat sign has to be coded as `.|:'. The command `\defineBarLine' provides an easy way to define additional bar line styles. * Accidentals in the key signature may be printed in octaves other than their traditional positions, or in multiple octaves.
2014-01-05 23:29:47 +01:00
@comment $NetBSD: PLIST,v 1.18 2014/01/05 22:29:47 wiz Exp $
Initial import of lilypond-1.3.86, the GNU music typesetter.
2000-10-15 19:32:11 +02:00
bin/abc2ly
Update to 1.3.119 because 1.3.86 didn't compile with python-2.0. Changes since 1.3.86: Lots of bugfixes, new info documentation, and some new functionality.
2000-12-28 18:04:23 +01:00
bin/convert-ly
bin/etf2ly
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
bin/lilymidi
Initial import of lilypond-1.3.86, the GNU music typesetter.
2000-10-15 19:32:11 +02:00
bin/lilypond
Update to 1.3.119 because 1.3.86 didn't compile with python-2.0. Changes since 1.3.86: Lots of bugfixes, new info documentation, and some new functionality.
2000-12-28 18:04:23 +01:00
bin/lilypond-book
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
bin/lilypond-invoke-editor
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
bin/lilysong
Initial import of lilypond-1.3.86, the GNU music typesetter.
2000-10-15 19:32:11 +02:00
bin/midi2ly
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
bin/musicxml2ly
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
info/lilypond-changes.info
info/lilypond-contributor.info
info/lilypond-essay.info
info/lilypond-extending.info
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
info/lilypond-internals.info
info/lilypond-learning.info
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
info/lilypond-notation.info
info/lilypond-usage.info
info/lilypond-web.info
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
info/music-glossary.info
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
lib/lilypond/${PKGVERSION}/python/midi.so
Initial import of lilypond-1.3.86, the GNU music typesetter.
2000-10-15 19:32:11 +02:00
man/man1/abc2ly.1
Update to 1.3.119 because 1.3.86 didn't compile with python-2.0. Changes since 1.3.86: Lots of bugfixes, new info documentation, and some new functionality.
2000-12-28 18:04:23 +01:00
man/man1/convert-ly.1
man/man1/etf2ly.1
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
man/man1/lilymidi.1
Update to 1.3.119 because 1.3.86 didn't compile with python-2.0. Changes since 1.3.86: Lots of bugfixes, new info documentation, and some new functionality.
2000-12-28 18:04:23 +01:00
man/man1/lilypond-book.1
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
man/man1/lilypond-invoke-editor.1
Initial import of lilypond-1.3.86, the GNU music typesetter.
2000-10-15 19:32:11 +02:00
man/man1/lilypond.1
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
man/man1/lilysong.1
Initial import of lilypond-1.3.86, the GNU music typesetter.
2000-10-15 19:32:11 +02:00
man/man1/midi2ly.1
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
man/man1/musicxml2ly.1
share/lilypond/${PKGVERSION}/fonts/otf/CenturySchL-Bold.otf
share/lilypond/${PKGVERSION}/fonts/otf/CenturySchL-BoldItal.otf
share/lilypond/${PKGVERSION}/fonts/otf/CenturySchL-Ital.otf
share/lilypond/${PKGVERSION}/fonts/otf/CenturySchL-Roma.otf
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-11.otf
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-13.otf
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-14.otf
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-16.otf
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-18.otf
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-20.otf
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-23.otf
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-26.otf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/otf/emmentaler-brace.otf
share/lilypond/${PKGVERSION}/fonts/source/feta-accidentals.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta-accordion.mf
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet11.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet13.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet14.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet16.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet18.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet20.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet23.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-alphabet26.mf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/source/feta-arrowheads.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta-autometric.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-a.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-b.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-c.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-d.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-e.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-f.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-g.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-h.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-braces-i.mf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/source/feta-braces.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-brackettips.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-clefs.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-dots.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-dynamics.mf
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta-flags-generic.mf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/source/feta-flags.mf
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta-flags11.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-flags13.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-flags14.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-flags16.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-flags18.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-flags20.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-flags23.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-flags26.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta-generic.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-macros.mf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads-generic.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads11.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads13.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads14.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads16.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads18.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads20.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads23.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-noteheads26.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-numbers.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta-params.mf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/source/feta-pedals.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-rests.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-scripts.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta-test-generic.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-test11.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-test13.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-test16.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-test20.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-test23.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-test26.mf
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta-ties.mf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/source/feta-timesignatures.mf
share/lilypond/${PKGVERSION}/fonts/source/feta-trills.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/feta11.mf
share/lilypond/${PKGVERSION}/fonts/source/feta13.mf
share/lilypond/${PKGVERSION}/fonts/source/feta14.mf
share/lilypond/${PKGVERSION}/fonts/source/feta16.mf
share/lilypond/${PKGVERSION}/fonts/source/feta18.mf
share/lilypond/${PKGVERSION}/fonts/source/feta20.mf
share/lilypond/${PKGVERSION}/fonts/source/feta23.mf
share/lilypond/${PKGVERSION}/fonts/source/feta26.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-accidentals.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-clefs.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-custodes.mf
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan-dots.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan-flags.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-generic.mf
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan-macros.mf
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads-generic.mf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads.mf
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads11.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads13.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads14.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads16.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads18.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads20.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads23.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-noteheads26.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan-rests.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan-scripts.mf
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan-timesignatures.mf
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/fonts/source/parmesan11.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan13.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan14.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan16.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan18.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan20.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan23.mf
share/lilypond/${PKGVERSION}/fonts/source/parmesan26.mf
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-11.svg
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-11.woff
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-13.svg
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-13.woff
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-14.svg
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-14.woff
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-16.svg
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-16.woff
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-18.svg
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-18.woff
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-20.svg
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-20.woff
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-23.svg
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-23.woff
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-26.svg
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-26.woff
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-brace.svg
share/lilypond/${PKGVERSION}/fonts/svg/emmentaler-brace.woff
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/ly/Welcome-to-LilyPond-MacOS.ly
share/lilypond/${PKGVERSION}/ly/Welcome_to_LilyPond.ly
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/ly/arabic.ly
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/ly/articulate.ly
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/ly/bagpipe.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/catalan.ly
share/lilypond/${PKGVERSION}/ly/chord-modifiers-init.ly
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/ly/chord-repetition-init.ly
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/ly/context-mods-init.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/declarations-init.ly
share/lilypond/${PKGVERSION}/ly/deutsch.ly
share/lilypond/${PKGVERSION}/ly/drumpitch-init.ly
share/lilypond/${PKGVERSION}/ly/dynamic-scripts-init.ly
share/lilypond/${PKGVERSION}/ly/english.ly
share/lilypond/${PKGVERSION}/ly/engraver-init.ly
share/lilypond/${PKGVERSION}/ly/espanol.ly
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/ly/event-listener.ly
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/ly/festival.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/generate-documentation.ly
share/lilypond/${PKGVERSION}/ly/generate-interface-doc-init.ly
share/lilypond/${PKGVERSION}/ly/grace-init.ly
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/ly/graphviz-init.ly
share/lilypond/${PKGVERSION}/ly/gregorian.ly
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/ly/guile-debugger.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/init.ly
share/lilypond/${PKGVERSION}/ly/italiano.ly
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/ly/lilypond-book-preamble.ly
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/ly/makam.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/midi-init.ly
share/lilypond/${PKGVERSION}/ly/music-functions-init.ly
share/lilypond/${PKGVERSION}/ly/nederlands.ly
share/lilypond/${PKGVERSION}/ly/norsk.ly
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/ly/paper-defaults-init.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/performer-init.ly
share/lilypond/${PKGVERSION}/ly/portugues.ly
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/ly/predefined-fretboards-init.ly
share/lilypond/${PKGVERSION}/ly/predefined-guitar-fretboards.ly
share/lilypond/${PKGVERSION}/ly/predefined-guitar-ninth-fretboards.ly
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/ly/predefined-mandolin-fretboards.ly
share/lilypond/${PKGVERSION}/ly/predefined-ukulele-fretboards.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/property-init.ly
share/lilypond/${PKGVERSION}/ly/scale-definitions-init.ly
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/ly/scheme-sandbox.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/script-init.ly
share/lilypond/${PKGVERSION}/ly/spanners-init.ly
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/ly/string-tunings-init.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/suomi.ly
share/lilypond/${PKGVERSION}/ly/svenska.ly
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/ly/text-replacements.ly
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/ly/titling-init.ly
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/ly/toc-init.ly
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/ly/vlaams.ly
share/lilypond/${PKGVERSION}/ps/lilyponddefs.ps
share/lilypond/${PKGVERSION}/ps/music-drawing-routines.ps
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/python/book_base.py
share/lilypond/${PKGVERSION}/python/book_base.pyc
share/lilypond/${PKGVERSION}/python/book_docbook.py
share/lilypond/${PKGVERSION}/python/book_docbook.pyc
share/lilypond/${PKGVERSION}/python/book_html.py
share/lilypond/${PKGVERSION}/python/book_html.pyc
share/lilypond/${PKGVERSION}/python/book_latex.py
share/lilypond/${PKGVERSION}/python/book_latex.pyc
share/lilypond/${PKGVERSION}/python/book_snippets.py
share/lilypond/${PKGVERSION}/python/book_snippets.pyc
share/lilypond/${PKGVERSION}/python/book_texinfo.py
share/lilypond/${PKGVERSION}/python/book_texinfo.pyc
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/python/convertrules.py
share/lilypond/${PKGVERSION}/python/convertrules.pyc
share/lilypond/${PKGVERSION}/python/fontextract.py
share/lilypond/${PKGVERSION}/python/fontextract.pyc
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/python/langdefs.py
share/lilypond/${PKGVERSION}/python/langdefs.pyc
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/python/lilylib.py
share/lilypond/${PKGVERSION}/python/lilylib.pyc
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/python/musicexp.py
share/lilypond/${PKGVERSION}/python/musicexp.pyc
share/lilypond/${PKGVERSION}/python/musicxml.py
share/lilypond/${PKGVERSION}/python/musicxml.pyc
share/lilypond/${PKGVERSION}/python/rational.py
share/lilypond/${PKGVERSION}/python/rational.pyc
share/lilypond/${PKGVERSION}/python/safeeval.py
share/lilypond/${PKGVERSION}/python/safeeval.pyc
Update to 2.18.0: New features in 2.18 since 2.16 ******************************* * There is now a new context type called `NullVoice' which, while not appearing in the printed output, can be used to align lyrics. This can be particularly convenient when used in parallel with a `\partcombine' construct. * Several articulations can be put into a single variable or returned from an event function. * The baseline of score markups is now taken from the reference point (usually the middle of the staff) of the first bottom system rather than the top of the bounding rectangle. * LilyPond no longer automatically infers a `\defaultchild' context in a context definition with `\accepts' clauses. Any context definition without an explicit or inherited `\defaultchild' definition counts as a `Bottom' context and will be eligible for rhythmic events and overrides without causing the implicit creation of other contexts. Be sure to specify a `\defaultchild' for non-`Bottom' contexts when defining them from scratch. * There is now extensive support for both discant and bass accordion register symbols in the `scm accreg' module. * New commands `markLengthOn' and `markLengthOff' control the allowance of horizontal space for tempo and rehearsal marks. * Rehearsal marks at the beginning of a line are now placed to the right of the clef and key signature by default. As in previous versions, the `break-alignable-interface' controls the behavior. * Decimal numbers can now be written directly in music, without a hash sign. Together with the previous change in the way object properties are specified, the code to change the length of stems has changed from this: \override Stem #'length = #5.6 e' f' g' a' to this: \override Stem.length = 5.6 e' f' g' a' One has to write a digit on both sides of the dot - values like `4.' or `-.3' are not allowed. Decimal fractions are also not accepted in `\chordmode'. * A number of shorthands like `(', `)', `|', `[', `]', `~', `\(', `\)' and others can now freely be redefined like normal commands. * The articulation shorthand for `\staccatissimo' has been renamed from `-|' to `-!'. * Tempo change ranges are now written as `\tempo 4 = 60 - 68' rather than `\tempo 4 = 60 ~ 68'. * Grob `OctavateEight' was renamed to `ClefModifier'. Related context properties were renamed from `xxxOctavationyyy' to `xxxTranspositionyyy'. * There is a new `\absolute' command explicitly marking music as being entered in absolute pitch. While this has been the default previously, an explicit `\absolute' also prevents reinterpretation when the passage is placed inside of `\relative'. * When `\relative' is used without an explicit reference pitch, the reference pitch now is the middle of the first octave, making the first entered pitch indistinguishable from absolute pitch. Previously, omitting the reference pitch would have lead to a default of `c''. Since that choice was somewhat arbitrary, recommended usage was to always specify the reference pitch. * A new command `\single' can be used for converting a property override into a tweak to be applied on a single music expression. * Two ways of letting graphical objects not appear in the output are overriding its `transparent' property with `#t' (retaining the original spacing) or overriding its `stencil' property with `#f' (not using any space at all). Those two operations now have the shorthands `\hide' and `\omit', respectively. * A new command `\temporary' can be applied to overrides in order to not have them replace previous property settings. If a `\revert' is applied to the same property subsequently, the previous setting reappears. This is mainly useful for writing music functions that need to have some property changed just for the duration of the function. * `\tag', `\removeWithTag', and `\keepWithTag' can now accept a list of symbols rather than just a single symbol for marking, removing, and keeping music with any of multiple tags. This is particularly important for `\keepWithTag' since one cannot achieve the same effect by using multiple consecutive `\keepWithTag' commands. * The `-d old-relative' option has been removed. Not actually accessible from the command line any more, its remaining use was for interpretating `\relative' in LilyPond files converted automatically from version 1.8 or older. It is unclear how much of this was actually still operative. * The meaning of `instrumentTransposition' has been reversed. After \set instrumentTransposition = #{ b #} a written `c'' now sounds like `b'. Previously, this would have been the other way round. This and the following change should make dealing with transposing instruments more straightforward. * The music generated by `\set' and `\override' commands is no longer affected by `\transpose'. The main consequence is that `\transpose' will transpose audible/concert pitch and printed pitch by the same amount even when the transposed music contains `\transposition'. Previously, \transpose c' f' \transposition bes' was equivalent to `\transposition f''. Now it stays equivalent to `\transposition bes''. * When checking for collisions, LilyPond no longer treats objects as rectangles. Instead, the actual shape of objects is approximated using an integral-like approach. This generally results in more even and snug positioning of objects and systems. Affected objects include `Accidentals', `Beams', `Clefs', `Dynamics', `FiguredBass', `Flags', `Glissandos', `Lyrics', `MetronomeMarks', `OttavaBrackets', `Pedals', `RehearsalMarks', `Rests', `Scripts', `TextScripts', `Ties', `Tuplets' and `VoltaBrackets'. * Tuplets are now created with the `\tuplet' command, which takes a fraction `T/N' to specify that T notes are played in the time usually allowed for N. One `\tuplet' command can create several tuplet groups if their duration is typed after the fraction. The `\times' command with its inverted fraction order `N/T' is still available. * Introducing two new markup-commands; `\draw-dashed-line' and `\draw-dotted-line'. The dashed-line extends to the whole length given by DEST, if `full-length' is set to `#t' (this is the default) without any space at the beginning or end. `off' will then be altered to fit. To insist on the given (or default) values of `on', `off' use `\override #'(full-length . #f)'. Manual settings for `on', `off' and `phase' are possible. The dotted-line always extends to the whole length given by DEST, without any space at the beginning or end. Manual settings for `off' are possible to get larger or smaller space between the dots. The given (or default) value of `off' will be altered to fit the line-length. * Starting with version 2.17.10, error messages or the `textedit' URI used for point-and-click functionality specify column numbers starting with 1 rather than 0. The byte offset (also part of `textedit' URIs) still starts at 0. * The `\clef' command supports optional transposition. * The LilyPond syntax of dot-separated words `Voice.Accidental' has been made interchangeable with `#'(Voice Accidental)', a Scheme list of symbols. * Grob and grob property path no longer need to be specified as two separate arguments to commands like `\override' and `\revert', allowing for the syntax \override Voice.TextSpanner.bound-details.left.text = "rit." Since complementary music functions like `\overrideProperty' cannot support forms with and without separating space at the same time, using a single dotted path is now the preferred form. Specifying grob path and grob property path separately, currently still supported with `\override' and `\revert' for compatibility reasons, is deprecated. * Due to words now being accepted as symbol function arguments, the interfaces of `\accidentalStyle', `\alterBroken', `\footnote' and `\tweak' had to be redesigned where optional symbol arguments were involved. Please check the respective music function documentation for details. * Several commands now accept symbol lists (conveniently entered as dot-separated words) for various kinds of arguments. These include `\accidentalStyle', `\alterBroken', `\footnote', `\hide', `\omit', `\overrideProperty', `\shape', and `\tweak'. * The bar line user interface has changed. Bar glyphs now resemble the appearance of the bar line, so a left repeat sign has to be coded as `.|:'. The command `\defineBarLine' provides an easy way to define additional bar line styles. * Accidentals in the key signature may be printed in octaves other than their traditional positions, or in multiple octaves.
2014-01-05 23:29:47 +01:00
share/lilypond/${PKGVERSION}/scm/accreg.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/auto-beam.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/autochange.scm
share/lilypond/${PKGVERSION}/scm/backend-library.scm
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/scm/bar-line.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/bezier-tools.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/c++.scm
share/lilypond/${PKGVERSION}/scm/chord-entry.scm
share/lilypond/${PKGVERSION}/scm/chord-generic-names.scm
share/lilypond/${PKGVERSION}/scm/chord-ignatzek-names.scm
share/lilypond/${PKGVERSION}/scm/chord-name.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/clip-region.scm
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/scm/coverage.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/define-context-properties.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/define-event-classes.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/define-grob-interfaces.scm
share/lilypond/${PKGVERSION}/scm/define-grob-properties.scm
share/lilypond/${PKGVERSION}/scm/define-grobs.scm
share/lilypond/${PKGVERSION}/scm/define-markup-commands.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/define-music-callbacks.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/define-music-display-methods.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/define-music-properties.scm
share/lilypond/${PKGVERSION}/scm/define-music-types.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/define-note-names.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/define-stencil-commands.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/define-woodwind-diagrams.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/display-lily.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/display-woodwind-diagrams.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/document-backend.scm
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/scm/document-context-mods.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/document-functions.scm
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/scm/document-identifiers.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/document-markup.scm
share/lilypond/${PKGVERSION}/scm/document-music.scm
share/lilypond/${PKGVERSION}/scm/document-translation.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/document-type-predicates.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/documentation-generate.scm
share/lilypond/${PKGVERSION}/scm/documentation-lib.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/editor.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/encoding.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/file-cache.scm
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/scm/flag-styles.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/font.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/framework-eps.scm
share/lilypond/${PKGVERSION}/scm/framework-null.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/framework-ps.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/framework-scm.scm
share/lilypond/${PKGVERSION}/scm/framework-socket.scm
share/lilypond/${PKGVERSION}/scm/framework-svg.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/fret-diagrams.scm
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/scm/graphviz.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/guile-debugger.scm
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/scm/harp-pedals.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/layout-beam.scm
share/lilypond/${PKGVERSION}/scm/layout-slur.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/lily-library.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/lily-sort.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/lily.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/ly-syntax-constructors.scm
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/scm/markup-macros.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/markup.scm
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/scm/memory-trace.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/midi.scm
share/lilypond/${PKGVERSION}/scm/modal-transforms.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/music-functions.scm
share/lilypond/${PKGVERSION}/scm/output-lib.scm
share/lilypond/${PKGVERSION}/scm/output-ps.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/output-socket.scm
share/lilypond/${PKGVERSION}/scm/output-svg.scm
share/lilypond/${PKGVERSION}/scm/page.scm
share/lilypond/${PKGVERSION}/scm/paper-system.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/paper.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/parser-clef.scm
share/lilypond/${PKGVERSION}/scm/parser-ly-from-scheme.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/part-combiner.scm
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/scm/predefined-fretboards.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/ps-to-png.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/safe-lily.scm
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/scm/safe-utility-defs.scm
Update to 2.18.0: New features in 2.18 since 2.16 ******************************* * There is now a new context type called `NullVoice' which, while not appearing in the printed output, can be used to align lyrics. This can be particularly convenient when used in parallel with a `\partcombine' construct. * Several articulations can be put into a single variable or returned from an event function. * The baseline of score markups is now taken from the reference point (usually the middle of the staff) of the first bottom system rather than the top of the bounding rectangle. * LilyPond no longer automatically infers a `\defaultchild' context in a context definition with `\accepts' clauses. Any context definition without an explicit or inherited `\defaultchild' definition counts as a `Bottom' context and will be eligible for rhythmic events and overrides without causing the implicit creation of other contexts. Be sure to specify a `\defaultchild' for non-`Bottom' contexts when defining them from scratch. * There is now extensive support for both discant and bass accordion register symbols in the `scm accreg' module. * New commands `markLengthOn' and `markLengthOff' control the allowance of horizontal space for tempo and rehearsal marks. * Rehearsal marks at the beginning of a line are now placed to the right of the clef and key signature by default. As in previous versions, the `break-alignable-interface' controls the behavior. * Decimal numbers can now be written directly in music, without a hash sign. Together with the previous change in the way object properties are specified, the code to change the length of stems has changed from this: \override Stem #'length = #5.6 e' f' g' a' to this: \override Stem.length = 5.6 e' f' g' a' One has to write a digit on both sides of the dot - values like `4.' or `-.3' are not allowed. Decimal fractions are also not accepted in `\chordmode'. * A number of shorthands like `(', `)', `|', `[', `]', `~', `\(', `\)' and others can now freely be redefined like normal commands. * The articulation shorthand for `\staccatissimo' has been renamed from `-|' to `-!'. * Tempo change ranges are now written as `\tempo 4 = 60 - 68' rather than `\tempo 4 = 60 ~ 68'. * Grob `OctavateEight' was renamed to `ClefModifier'. Related context properties were renamed from `xxxOctavationyyy' to `xxxTranspositionyyy'. * There is a new `\absolute' command explicitly marking music as being entered in absolute pitch. While this has been the default previously, an explicit `\absolute' also prevents reinterpretation when the passage is placed inside of `\relative'. * When `\relative' is used without an explicit reference pitch, the reference pitch now is the middle of the first octave, making the first entered pitch indistinguishable from absolute pitch. Previously, omitting the reference pitch would have lead to a default of `c''. Since that choice was somewhat arbitrary, recommended usage was to always specify the reference pitch. * A new command `\single' can be used for converting a property override into a tweak to be applied on a single music expression. * Two ways of letting graphical objects not appear in the output are overriding its `transparent' property with `#t' (retaining the original spacing) or overriding its `stencil' property with `#f' (not using any space at all). Those two operations now have the shorthands `\hide' and `\omit', respectively. * A new command `\temporary' can be applied to overrides in order to not have them replace previous property settings. If a `\revert' is applied to the same property subsequently, the previous setting reappears. This is mainly useful for writing music functions that need to have some property changed just for the duration of the function. * `\tag', `\removeWithTag', and `\keepWithTag' can now accept a list of symbols rather than just a single symbol for marking, removing, and keeping music with any of multiple tags. This is particularly important for `\keepWithTag' since one cannot achieve the same effect by using multiple consecutive `\keepWithTag' commands. * The `-d old-relative' option has been removed. Not actually accessible from the command line any more, its remaining use was for interpretating `\relative' in LilyPond files converted automatically from version 1.8 or older. It is unclear how much of this was actually still operative. * The meaning of `instrumentTransposition' has been reversed. After \set instrumentTransposition = #{ b #} a written `c'' now sounds like `b'. Previously, this would have been the other way round. This and the following change should make dealing with transposing instruments more straightforward. * The music generated by `\set' and `\override' commands is no longer affected by `\transpose'. The main consequence is that `\transpose' will transpose audible/concert pitch and printed pitch by the same amount even when the transposed music contains `\transposition'. Previously, \transpose c' f' \transposition bes' was equivalent to `\transposition f''. Now it stays equivalent to `\transposition bes''. * When checking for collisions, LilyPond no longer treats objects as rectangles. Instead, the actual shape of objects is approximated using an integral-like approach. This generally results in more even and snug positioning of objects and systems. Affected objects include `Accidentals', `Beams', `Clefs', `Dynamics', `FiguredBass', `Flags', `Glissandos', `Lyrics', `MetronomeMarks', `OttavaBrackets', `Pedals', `RehearsalMarks', `Rests', `Scripts', `TextScripts', `Ties', `Tuplets' and `VoltaBrackets'. * Tuplets are now created with the `\tuplet' command, which takes a fraction `T/N' to specify that T notes are played in the time usually allowed for N. One `\tuplet' command can create several tuplet groups if their duration is typed after the fraction. The `\times' command with its inverted fraction order `N/T' is still available. * Introducing two new markup-commands; `\draw-dashed-line' and `\draw-dotted-line'. The dashed-line extends to the whole length given by DEST, if `full-length' is set to `#t' (this is the default) without any space at the beginning or end. `off' will then be altered to fit. To insist on the given (or default) values of `on', `off' use `\override #'(full-length . #f)'. Manual settings for `on', `off' and `phase' are possible. The dotted-line always extends to the whole length given by DEST, without any space at the beginning or end. Manual settings for `off' are possible to get larger or smaller space between the dots. The given (or default) value of `off' will be altered to fit the line-length. * Starting with version 2.17.10, error messages or the `textedit' URI used for point-and-click functionality specify column numbers starting with 1 rather than 0. The byte offset (also part of `textedit' URIs) still starts at 0. * The `\clef' command supports optional transposition. * The LilyPond syntax of dot-separated words `Voice.Accidental' has been made interchangeable with `#'(Voice Accidental)', a Scheme list of symbols. * Grob and grob property path no longer need to be specified as two separate arguments to commands like `\override' and `\revert', allowing for the syntax \override Voice.TextSpanner.bound-details.left.text = "rit." Since complementary music functions like `\overrideProperty' cannot support forms with and without separating space at the same time, using a single dotted path is now the preferred form. Specifying grob path and grob property path separately, currently still supported with `\override' and `\revert' for compatibility reasons, is deprecated. * Due to words now being accepted as symbol function arguments, the interfaces of `\accidentalStyle', `\alterBroken', `\footnote' and `\tweak' had to be redesigned where optional symbol arguments were involved. Please check the respective music function documentation for details. * Several commands now accept symbol lists (conveniently entered as dot-separated words) for various kinds of arguments. These include `\accidentalStyle', `\alterBroken', `\footnote', `\hide', `\omit', `\overrideProperty', `\shape', and `\tweak'. * The bar line user interface has changed. Bar glyphs now resemble the appearance of the bar line, so a left repeat sign has to be coded as `.|:'. The command `\defineBarLine' provides an easy way to define additional bar line styles. * Accidentals in the key signature may be printed in octaves other than their traditional positions, or in multiple octaves.
2014-01-05 23:29:47 +01:00
share/lilypond/${PKGVERSION}/scm/scheme-engravers.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/script.scm
Update to 2.18.0: New features in 2.18 since 2.16 ******************************* * There is now a new context type called `NullVoice' which, while not appearing in the printed output, can be used to align lyrics. This can be particularly convenient when used in parallel with a `\partcombine' construct. * Several articulations can be put into a single variable or returned from an event function. * The baseline of score markups is now taken from the reference point (usually the middle of the staff) of the first bottom system rather than the top of the bounding rectangle. * LilyPond no longer automatically infers a `\defaultchild' context in a context definition with `\accepts' clauses. Any context definition without an explicit or inherited `\defaultchild' definition counts as a `Bottom' context and will be eligible for rhythmic events and overrides without causing the implicit creation of other contexts. Be sure to specify a `\defaultchild' for non-`Bottom' contexts when defining them from scratch. * There is now extensive support for both discant and bass accordion register symbols in the `scm accreg' module. * New commands `markLengthOn' and `markLengthOff' control the allowance of horizontal space for tempo and rehearsal marks. * Rehearsal marks at the beginning of a line are now placed to the right of the clef and key signature by default. As in previous versions, the `break-alignable-interface' controls the behavior. * Decimal numbers can now be written directly in music, without a hash sign. Together with the previous change in the way object properties are specified, the code to change the length of stems has changed from this: \override Stem #'length = #5.6 e' f' g' a' to this: \override Stem.length = 5.6 e' f' g' a' One has to write a digit on both sides of the dot - values like `4.' or `-.3' are not allowed. Decimal fractions are also not accepted in `\chordmode'. * A number of shorthands like `(', `)', `|', `[', `]', `~', `\(', `\)' and others can now freely be redefined like normal commands. * The articulation shorthand for `\staccatissimo' has been renamed from `-|' to `-!'. * Tempo change ranges are now written as `\tempo 4 = 60 - 68' rather than `\tempo 4 = 60 ~ 68'. * Grob `OctavateEight' was renamed to `ClefModifier'. Related context properties were renamed from `xxxOctavationyyy' to `xxxTranspositionyyy'. * There is a new `\absolute' command explicitly marking music as being entered in absolute pitch. While this has been the default previously, an explicit `\absolute' also prevents reinterpretation when the passage is placed inside of `\relative'. * When `\relative' is used without an explicit reference pitch, the reference pitch now is the middle of the first octave, making the first entered pitch indistinguishable from absolute pitch. Previously, omitting the reference pitch would have lead to a default of `c''. Since that choice was somewhat arbitrary, recommended usage was to always specify the reference pitch. * A new command `\single' can be used for converting a property override into a tweak to be applied on a single music expression. * Two ways of letting graphical objects not appear in the output are overriding its `transparent' property with `#t' (retaining the original spacing) or overriding its `stencil' property with `#f' (not using any space at all). Those two operations now have the shorthands `\hide' and `\omit', respectively. * A new command `\temporary' can be applied to overrides in order to not have them replace previous property settings. If a `\revert' is applied to the same property subsequently, the previous setting reappears. This is mainly useful for writing music functions that need to have some property changed just for the duration of the function. * `\tag', `\removeWithTag', and `\keepWithTag' can now accept a list of symbols rather than just a single symbol for marking, removing, and keeping music with any of multiple tags. This is particularly important for `\keepWithTag' since one cannot achieve the same effect by using multiple consecutive `\keepWithTag' commands. * The `-d old-relative' option has been removed. Not actually accessible from the command line any more, its remaining use was for interpretating `\relative' in LilyPond files converted automatically from version 1.8 or older. It is unclear how much of this was actually still operative. * The meaning of `instrumentTransposition' has been reversed. After \set instrumentTransposition = #{ b #} a written `c'' now sounds like `b'. Previously, this would have been the other way round. This and the following change should make dealing with transposing instruments more straightforward. * The music generated by `\set' and `\override' commands is no longer affected by `\transpose'. The main consequence is that `\transpose' will transpose audible/concert pitch and printed pitch by the same amount even when the transposed music contains `\transposition'. Previously, \transpose c' f' \transposition bes' was equivalent to `\transposition f''. Now it stays equivalent to `\transposition bes''. * When checking for collisions, LilyPond no longer treats objects as rectangles. Instead, the actual shape of objects is approximated using an integral-like approach. This generally results in more even and snug positioning of objects and systems. Affected objects include `Accidentals', `Beams', `Clefs', `Dynamics', `FiguredBass', `Flags', `Glissandos', `Lyrics', `MetronomeMarks', `OttavaBrackets', `Pedals', `RehearsalMarks', `Rests', `Scripts', `TextScripts', `Ties', `Tuplets' and `VoltaBrackets'. * Tuplets are now created with the `\tuplet' command, which takes a fraction `T/N' to specify that T notes are played in the time usually allowed for N. One `\tuplet' command can create several tuplet groups if their duration is typed after the fraction. The `\times' command with its inverted fraction order `N/T' is still available. * Introducing two new markup-commands; `\draw-dashed-line' and `\draw-dotted-line'. The dashed-line extends to the whole length given by DEST, if `full-length' is set to `#t' (this is the default) without any space at the beginning or end. `off' will then be altered to fit. To insist on the given (or default) values of `on', `off' use `\override #'(full-length . #f)'. Manual settings for `on', `off' and `phase' are possible. The dotted-line always extends to the whole length given by DEST, without any space at the beginning or end. Manual settings for `off' are possible to get larger or smaller space between the dots. The given (or default) value of `off' will be altered to fit the line-length. * Starting with version 2.17.10, error messages or the `textedit' URI used for point-and-click functionality specify column numbers starting with 1 rather than 0. The byte offset (also part of `textedit' URIs) still starts at 0. * The `\clef' command supports optional transposition. * The LilyPond syntax of dot-separated words `Voice.Accidental' has been made interchangeable with `#'(Voice Accidental)', a Scheme list of symbols. * Grob and grob property path no longer need to be specified as two separate arguments to commands like `\override' and `\revert', allowing for the syntax \override Voice.TextSpanner.bound-details.left.text = "rit." Since complementary music functions like `\overrideProperty' cannot support forms with and without separating space at the same time, using a single dotted path is now the preferred form. Specifying grob path and grob property path separately, currently still supported with `\override' and `\revert' for compatibility reasons, is deprecated. * Due to words now being accepted as symbol function arguments, the interfaces of `\accidentalStyle', `\alterBroken', `\footnote' and `\tweak' had to be redesigned where optional symbol arguments were involved. Please check the respective music function documentation for details. * Several commands now accept symbol lists (conveniently entered as dot-separated words) for various kinds of arguments. These include `\accidentalStyle', `\alterBroken', `\footnote', `\hide', `\omit', `\overrideProperty', `\shape', and `\tweak'. * The bar line user interface has changed. Bar glyphs now resemble the appearance of the bar line, so a left repeat sign has to be coded as `.|:'. The command `\defineBarLine' provides an easy way to define additional bar line styles. * Accidentals in the key signature may be printed in octaves other than their traditional positions, or in multiple octaves.
2014-01-05 23:29:47 +01:00
share/lilypond/${PKGVERSION}/scm/skyline.scm
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/lilypond/${PKGVERSION}/scm/song-util.scm
share/lilypond/${PKGVERSION}/scm/song.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/standalone.scm
share/lilypond/${PKGVERSION}/scm/stencil.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/tablature.scm
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/lilypond/${PKGVERSION}/scm/text.scm
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/scm/time-signature-settings.scm
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/scm/titling.scm
share/lilypond/${PKGVERSION}/scm/to-xml.scm
share/lilypond/${PKGVERSION}/scm/translation-functions.scm
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/lilypond/${PKGVERSION}/scm/x11-color.scm
share/lilypond/${PKGVERSION}/tex/lilypond-tex-metrics.tex
update to lilypond-2.4.3. This represents a major version bump and with it many many improvements and changes which are far to long to summarize here. One important change is that this version works with gcc3.
2004-12-30 06:11:57 +01:00
share/lilypond/${PKGVERSION}/vim/compiler/lilypond.vim
share/lilypond/${PKGVERSION}/vim/ftdetect/lilypond.vim
share/lilypond/${PKGVERSION}/vim/ftplugin/lilypond.vim
share/lilypond/${PKGVERSION}/vim/indent/lilypond.vim
share/lilypond/${PKGVERSION}/vim/syntax/lilypond-words
share/lilypond/${PKGVERSION}/vim/syntax/lilypond-words.vim
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/lilypond/${PKGVERSION}/vim/syntax/lilypond.vim
Update to 2.18.0: New features in 2.18 since 2.16 ******************************* * There is now a new context type called `NullVoice' which, while not appearing in the printed output, can be used to align lyrics. This can be particularly convenient when used in parallel with a `\partcombine' construct. * Several articulations can be put into a single variable or returned from an event function. * The baseline of score markups is now taken from the reference point (usually the middle of the staff) of the first bottom system rather than the top of the bounding rectangle. * LilyPond no longer automatically infers a `\defaultchild' context in a context definition with `\accepts' clauses. Any context definition without an explicit or inherited `\defaultchild' definition counts as a `Bottom' context and will be eligible for rhythmic events and overrides without causing the implicit creation of other contexts. Be sure to specify a `\defaultchild' for non-`Bottom' contexts when defining them from scratch. * There is now extensive support for both discant and bass accordion register symbols in the `scm accreg' module. * New commands `markLengthOn' and `markLengthOff' control the allowance of horizontal space for tempo and rehearsal marks. * Rehearsal marks at the beginning of a line are now placed to the right of the clef and key signature by default. As in previous versions, the `break-alignable-interface' controls the behavior. * Decimal numbers can now be written directly in music, without a hash sign. Together with the previous change in the way object properties are specified, the code to change the length of stems has changed from this: \override Stem #'length = #5.6 e' f' g' a' to this: \override Stem.length = 5.6 e' f' g' a' One has to write a digit on both sides of the dot - values like `4.' or `-.3' are not allowed. Decimal fractions are also not accepted in `\chordmode'. * A number of shorthands like `(', `)', `|', `[', `]', `~', `\(', `\)' and others can now freely be redefined like normal commands. * The articulation shorthand for `\staccatissimo' has been renamed from `-|' to `-!'. * Tempo change ranges are now written as `\tempo 4 = 60 - 68' rather than `\tempo 4 = 60 ~ 68'. * Grob `OctavateEight' was renamed to `ClefModifier'. Related context properties were renamed from `xxxOctavationyyy' to `xxxTranspositionyyy'. * There is a new `\absolute' command explicitly marking music as being entered in absolute pitch. While this has been the default previously, an explicit `\absolute' also prevents reinterpretation when the passage is placed inside of `\relative'. * When `\relative' is used without an explicit reference pitch, the reference pitch now is the middle of the first octave, making the first entered pitch indistinguishable from absolute pitch. Previously, omitting the reference pitch would have lead to a default of `c''. Since that choice was somewhat arbitrary, recommended usage was to always specify the reference pitch. * A new command `\single' can be used for converting a property override into a tweak to be applied on a single music expression. * Two ways of letting graphical objects not appear in the output are overriding its `transparent' property with `#t' (retaining the original spacing) or overriding its `stencil' property with `#f' (not using any space at all). Those two operations now have the shorthands `\hide' and `\omit', respectively. * A new command `\temporary' can be applied to overrides in order to not have them replace previous property settings. If a `\revert' is applied to the same property subsequently, the previous setting reappears. This is mainly useful for writing music functions that need to have some property changed just for the duration of the function. * `\tag', `\removeWithTag', and `\keepWithTag' can now accept a list of symbols rather than just a single symbol for marking, removing, and keeping music with any of multiple tags. This is particularly important for `\keepWithTag' since one cannot achieve the same effect by using multiple consecutive `\keepWithTag' commands. * The `-d old-relative' option has been removed. Not actually accessible from the command line any more, its remaining use was for interpretating `\relative' in LilyPond files converted automatically from version 1.8 or older. It is unclear how much of this was actually still operative. * The meaning of `instrumentTransposition' has been reversed. After \set instrumentTransposition = #{ b #} a written `c'' now sounds like `b'. Previously, this would have been the other way round. This and the following change should make dealing with transposing instruments more straightforward. * The music generated by `\set' and `\override' commands is no longer affected by `\transpose'. The main consequence is that `\transpose' will transpose audible/concert pitch and printed pitch by the same amount even when the transposed music contains `\transposition'. Previously, \transpose c' f' \transposition bes' was equivalent to `\transposition f''. Now it stays equivalent to `\transposition bes''. * When checking for collisions, LilyPond no longer treats objects as rectangles. Instead, the actual shape of objects is approximated using an integral-like approach. This generally results in more even and snug positioning of objects and systems. Affected objects include `Accidentals', `Beams', `Clefs', `Dynamics', `FiguredBass', `Flags', `Glissandos', `Lyrics', `MetronomeMarks', `OttavaBrackets', `Pedals', `RehearsalMarks', `Rests', `Scripts', `TextScripts', `Ties', `Tuplets' and `VoltaBrackets'. * Tuplets are now created with the `\tuplet' command, which takes a fraction `T/N' to specify that T notes are played in the time usually allowed for N. One `\tuplet' command can create several tuplet groups if their duration is typed after the fraction. The `\times' command with its inverted fraction order `N/T' is still available. * Introducing two new markup-commands; `\draw-dashed-line' and `\draw-dotted-line'. The dashed-line extends to the whole length given by DEST, if `full-length' is set to `#t' (this is the default) without any space at the beginning or end. `off' will then be altered to fit. To insist on the given (or default) values of `on', `off' use `\override #'(full-length . #f)'. Manual settings for `on', `off' and `phase' are possible. The dotted-line always extends to the whole length given by DEST, without any space at the beginning or end. Manual settings for `off' are possible to get larger or smaller space between the dots. The given (or default) value of `off' will be altered to fit the line-length. * Starting with version 2.17.10, error messages or the `textedit' URI used for point-and-click functionality specify column numbers starting with 1 rather than 0. The byte offset (also part of `textedit' URIs) still starts at 0. * The `\clef' command supports optional transposition. * The LilyPond syntax of dot-separated words `Voice.Accidental' has been made interchangeable with `#'(Voice Accidental)', a Scheme list of symbols. * Grob and grob property path no longer need to be specified as two separate arguments to commands like `\override' and `\revert', allowing for the syntax \override Voice.TextSpanner.bound-details.left.text = "rit." Since complementary music functions like `\overrideProperty' cannot support forms with and without separating space at the same time, using a single dotted path is now the preferred form. Specifying grob path and grob property path separately, currently still supported with `\override' and `\revert' for compatibility reasons, is deprecated. * Due to words now being accepted as symbol function arguments, the interfaces of `\accidentalStyle', `\alterBroken', `\footnote' and `\tweak' had to be redesigned where optional symbol arguments were involved. Please check the respective music function documentation for details. * Several commands now accept symbol lists (conveniently entered as dot-separated words) for various kinds of arguments. These include `\accidentalStyle', `\alterBroken', `\footnote', `\hide', `\omit', `\overrideProperty', `\shape', and `\tweak'. * The bar line user interface has changed. Bar glyphs now resemble the appearance of the bar line, so a left repeat sign has to be coded as `.|:'. The command `\defineBarLine' provides an easy way to define additional bar line styles. * Accidentals in the key signature may be printed in octaves other than their traditional positions, or in multiple octaves.
2014-01-05 23:29:47 +01:00
share/locale/ca/LC_MESSAGES/lilypond.mo
Strip ${PKGLOCALEDIR} from PLISTs of packages that already obey PKGLOCALEDIR and which install their locale files directly under ${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now on, pkgsrc/mk/plist/plist-locale.awk will automatically handle transforming the PLIST to refer to the correct locale directory.
2006-04-17 09:07:11 +02:00
share/locale/cs/LC_MESSAGES/lilypond.mo
share/locale/da/LC_MESSAGES/lilypond.mo
share/locale/de/LC_MESSAGES/lilypond.mo
Update to 2.14.2 * Update MASTER_SITES. Changelog: * New scripts introduced. * MIDI input and output are improved. * Some notation improvements. * Some new signs are introduced. * Unicode Bidirectional Algorithm is fully supported. * and so on. see NEWS.txt.
2011-07-31 11:12:46 +02:00
share/locale/el/LC_MESSAGES/lilypond.mo
Update to 2.16.2. Comment patches. Fixes and changes after 2.16.0 ============================== 2.16.1 Please refer to the bug tracker for issues fixed in 2.16.1 (http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1). New features in 2.16 since 2.14 =============================== * Support for cross-staff stems on chords, using `crossStaff' and the `Span_stem_engraver'. This calculates the length of cross-staff stems automatically. * The syntax of words (character sequences recognized without enclosing quotes) and commands (now always a backslash `\' followed by a word) has been unified across all modes: it now consists of alphabetic characters, possibly enclosing isolated dashes `-' and underlines `_'. As one consequence, using unquoted text scripts like (literally!) { c-script c\f_script } will now tend to result in invalid music. Omitting quote marks for arbitrary text rather than keywords has never been good practice or even documented, and it is unlikely to have seen significant use. Staying with established conventions (like not using dashes or underlines for command names intended to be used inside of music) remains advisable. The reason for this change is more robust recognition of LilyPond's lexical units for LilyPond itself as well as external tools interpreting its syntax. * Support for Kievan square notation: \new KievanVoice { \cadenzaOn c d e f g a bes \bar "kievan" } * Augmentation dots now avoid the other voice in two-voice polyphony so that users can move the `Dot_column_engraver' to set dots independently for each `Voice'. * A Scheme function to adjust the control points of curves such as slurs and ties, developed by several users, is now included in LilyPond. g8->( bes,-.) d4 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) g8->( bes,!-.) d4 * Use of `\tempo' specifications in `\midi' blocks (removed in 2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has seen a revival: now any kind of property-setting music is turned into context definitions within output specifications, allowing for declarations like \layout { \accidentalStyle modern } \midi { \tempo 4. = 66 } * The LilyPond G clef has been redesigned - upper loop is now more balanced, bottom crook sticks out less and the "spine" (main vertical line) is more evenly curved. The old and new versions can be compared by looking at the documentation: old version (http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs), new version (http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs). * Lilypond's stencil commands have been simplified to allow for less code duplication and better height approximations of graphical objects. The following stencil commands have been eliminated: * `beam' * `bezier-sandwich' * `bracket' * `dashed-slur' * `dot' * `oval' * `repeat-slash' * `zigzag-line' * Flags are now treated as separate objects rather than as stem parts. * Two alternative methods for bar numbering can be set, especially for when using repeated music; * The following is a fundamental change in LilyPond's music representation: Rhythmic events like `LyricEvent' and `NoteEvent' are no longer wrapped in `EventChord' unless they have been actually entered as part of a chord in the input. If you manipulate music expressions in Scheme, the new behavior may require changes in your code. Calling the music function `\eventChords' or the Scheme function `event-chord-wrap!' converts to the old representation; using one of those might be easiest for keeping legacy code operative. The following three items are consequences of this change. * The repetitive chord entry aid `q' has been reimplemented. Repeated chords are now replaced right before interpreting a music expression. In case the user wants to retain some events of the original chord, he can run the repeat chord replacement function `\chordRepeats' manually. * String numbers and right hand fingerings on single notes now appear without having to be written inside of chord brackets. * Music functions now work the same when used inside or outside of chords, including all the possibilities of argument parsing. Music variables can be used inside of chords: a construct like tonic=fis' { <\tonic \transpose c g \tonic> } now works as expected. One can use `#{...#}' for constructing chord constituents. `\tweak' now works on single notes without needing to wrap them in a chord. Using it on command events and lyrics is now possible, but not likely to give results yet. * `\tweak' now takes an optional layout object specification. It can be used for tweaking layout objects that are only indirectly caused by the tweaked event, like accidentals, stems, and flags: <\tweak Accidental #'color #red cis4 \tweak Accidental #'color #green es g> * Scheme expressions inside of embedded Lilypond (`#{...#}') are now executed in lexical closure of the surrounding Scheme code. `$' is no longer special in embedded Lilypond. It can be used unconditionally in Lilypond code for immediate evaluation of Scheme expressions, similar to how `ly:export' could previously be used. `ly:export' has been removed. As a consequence, `#' is now free to delay evaluation of its argument until the parser actually reduces the containing expression, greatly reducing the potential for premature evaluation. There are also `splicing' operators `$@' and `#@' for interpreting the members of a list individually. * To reduce the necessity for using `$', Scheme expressions written with `#' are interpreted as music inside of music lists, and as markups or markup lists inside of markups. * Support for jazz-like chords has been improved: Lydian and altered chords are recognised; separators between chord modifiers are now treated independently of separators between "slash" chords and their bass notes (and by default, slashes are now only used for the latter type of separator); additional pitches are no longer prefixed with "add" by default; and the "m" in minor chords can be customized. *note Customizing chord names: (lilypond-notation)Customizing chord names. for more information. * The `\markuplines' command has been renamed to `\markuplist' for a better match with its semantics and general Lilypond nomenclature. * The interface for specifying string tunings in tablature has been simplified considerably and employs the scheme function `\stringTuning' for most purposes. * Beams can now have their slopes preserved over line breaks. To do this, several callback functions are now deprecated. * `ly:beam::calc-least-squares-positions' * `ly:beam::slope-damping' * `ly:beam::shift-region-to-valid' Furthermore, `ly:beam::quanting' now takes an additional argument to help calculations over line breaks. All of these functions are now automatically called when setting the `positions' parameter. * In function arguments music, markups and Scheme expressions (as well as several other syntactic entities) have become mostly interchangeable and are told apart only by evaluating the respective predicate. In several cases, the predicate is consulted by the parser, like when deciding whether to interpret `-3' as a number or a fingering event. * Music functions (and their close relatives) can now be defined with optional arguments. * For defining commands executed only for their side-effects, `define-void-function' is now available. * There is a new `define-event-function' command in analogy to `define-music-function' that can be used for defining music functions acting as post events without requiring a direction specifier (`-', `^', or `_') placed before them. dyn=#(define-event-function (parser location arg) (markup?) (make-dynamic-script arg)) \relative c' { c\dyn pfsss } * A list of ASCII aliases for special characters can be included. \paper { #(include-special-characters) } \markup "&bull; &dagger; &copyright; &OE; &ss; &para;" * There is a new `define-scheme-function' command in analogy to `define-music-function' that can be used to define functions evaluating to Scheme expressions while accepting arguments in Lilypond syntax. * The construct `#{ ... #}' can now be used not just for constructing sequential music lists, but also for pitches (distinguished from single note events by the absence of a duration or other information that can't be part of a pitch), single music events, void music expressions, post events, markups (mostly freeing users from having to use the `markup' macro), markup lists, number expressions, context definitions and modifications, and a few other things. If it encloses nothing or only a single music event, it no longer returns a sequential music list but rather a void music expression or just the music event itself, respectively. * Pitches can be used on the right side of assignments. They are distinguished from single note events by the absence of a duration or other information that can't be part of a pitch. * New command-line option `--loglevel=LEVEL' to control how much output LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. * `\once \set' now correctly resets the property value to the previous value. * The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now automatically broken if a different direction is explicitly given. * Appoggiaturas and acciaccaturas now also work inside a slur, not only inside a phrasing slur. Also, a function `\slashedGrace' was added that does not use a slur from the acciaccatura note. * To suppress the line on a crescendo text spanner (and other similar spanners), LilyPond now fully supports the `#'style = #'none' property. * LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! * Glissandi can now span multiple lines.
2013-01-25 12:32:07 +01:00
share/locale/eo/LC_MESSAGES/lilypond.mo
Strip ${PKGLOCALEDIR} from PLISTs of packages that already obey PKGLOCALEDIR and which install their locale files directly under ${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now on, pkgsrc/mk/plist/plist-locale.awk will automatically handle transforming the PLIST to refer to the correct locale directory.
2006-04-17 09:07:11 +02:00
share/locale/es/LC_MESSAGES/lilypond.mo
share/locale/fi/LC_MESSAGES/lilypond.mo
share/locale/fr/LC_MESSAGES/lilypond.mo
share/locale/it/LC_MESSAGES/lilypond.mo
share/locale/ja/LC_MESSAGES/lilypond.mo
share/locale/nl/LC_MESSAGES/lilypond.mo
share/locale/ru/LC_MESSAGES/lilypond.mo
share/locale/sv/LC_MESSAGES/lilypond.mo
share/locale/tr/LC_MESSAGES/lilypond.mo
Update to 2.12.2. The list of upstream changes is too massive to put it here (almost two years of development). http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html has nice list of new features.
2009-06-03 21:52:33 +02:00
share/locale/uk/LC_MESSAGES/lilypond.mo
share/locale/vi/LC_MESSAGES/lilypond.mo
Update to 2.10.33. Changes are too numerous to mention. N.B. I've removed the dependency on emacs, it was only used to create the folder to install a single folder in and worse still, PLIST used EMACS_LISPPREFIX but this wasn't used by Lilypond.
2008-05-14 22:25:15 +02:00
share/locale/zh_TW/LC_MESSAGES/lilypond.mo
Reference in a new issue Copy permalink