X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fchanges.tely;h=951dabd22bf86dbba406bf8e05e3fe5f7c6d9f19;hb=ab567eadd06d56149fc59b6d17ee40a27e77a467;hp=912800a3a1578a0b38a466ccf47a85f72304dad9;hpb=3c169262c8f580c0f42c09f3a61b9ae9f0d6261c;p=lilypond.git diff --git a/Documentation/changes.tely b/Documentation/changes.tely index 912800a3a1..951dabd22b 100644 --- a/Documentation/changes.tely +++ b/Documentation/changes.tely @@ -36,7 +36,7 @@ See user manual, \NAME\ @finalout @node Top -@top New features in 2.16 since 2.14 +@top New features in 2.18 since 2.16 @allowcodebreaks false @@ -60,327 +60,225 @@ which scares away people. * only show user-visible changes. @end ignore -@item -Support for Kievan square notation: -@lilypond[quote,relative=1,verbatim] -\new KievanVoice { - \cadenzaOn - c d e f g a bes - \bar "kievan" -} -@end lilypond @item -Augmentation dots now avoid the other voice in two-voice polyphony -so that users can move the @code{Dot_column_engraver} to set dots -independently for each @code{Voice}. -@lilypond[quote] -\layout { - \context { - \Staff - \remove Dot_column_engraver - } \context { - \Voice - \consists Dot_column_engraver - } -} -\relative c'' << - { \time 6/8 - 4. b - } \\ { - 4. - } >> -@end lilypond +When @code{\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 @code{c'}. Since that choice was somewhat arbitrary, +recommended usage was to always specify the reference pitch. @item -A Scheme function to adjust the control points of curves such as slurs -and ties, developed by several users, is now included in LilyPond. +A new command @code{\single} can be used for converting a property +override into a tweak to be applied on a single music expression: + @lilypond[quote,verbatim,relative=2] -g8->( bes,-.) d4 -\shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) -g8->( bes,!-.) d4 +1 @end lilypond @item -Use of @code{\tempo} specifications in @code{\midi} blocks (removed in -2.9.16 in favor of explicit @code{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 -@example -\layout @{ \accidentalStyle modern @} -\midi @{ \tempo 4. = 66 @} -@end example - -@item -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: -@uref{http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs, old version}, -@uref{http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs, new version}. - -@item -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: -@itemize -@item @code{beam} -@item @code{bezier-sandwich} -@item @code{bracket} -@item @code{dashed-slur} -@item @code{dot} -@item @code{oval} -@item @code{repeat-slash} -@item @code{zigzag-line} -@end itemize +Two ways of letting graphical objects not appear in the output are +overriding its @code{transparent} property with @code{#t} +(retaining the original spacing) or overriding its @code{stencil} +property with @code{#f} (not using any space at all). Those two +operations now have the shorthands @code{\hide} and @code{\omit}, +respectively. They can either be given a music expression to +tweak, or the name of a graphical object for which an override +should be created (for specifying both, use @code{\single} on the +override form): -@item -Flags are now treated as separate objects rather than as stem parts. -@lilypond[fragment,quote,relative=2] -\override Flag #'color = #red -g8 -@end lilypond - -@item -Two alternative methods for bar numbering can be set, especially for -when using repeated music; - -@lilypond[fragment,quote,relative=1,noragged-right] -\relative c'{ - \set Score.alternativeNumberingStyle = #'numbers - \repeat volta 3 { c4 d e f | } - \alternative { - { c4 d e f | c2 d \break } - { f4 g a b | f4 g a b | f2 a | \break } - { c4 d e f | c2 d } - } - c1 \break - \set Score.alternativeNumberingStyle = #'numbers-with-letters - \repeat volta 3 { c,4 d e f | } - \alternative { - { c4 d e f | c2 d \break } - { f4 g a b | f4 g a b | f2 a | \break } - { c4 d e f | c2 d } - } - c1 -} +@lilypond[quote,verbatim] +\new Staff \with { \omit Clef } +\relative c'' 1 @end lilypond @item -The following is a fundamental change in LilyPond's music -representation: Rhythmic events like @code{LyricEvent} and -@code{NoteEvent} are no longer wrapped in @code{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 @code{\eventChords} or -the Scheme function @code{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. - -@item -The repetitive chord entry aid @code{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 -@code{\chordRepeats} manually. - -@item -String numbers and right hand fingerings on single notes now appear -without having to be written inside of chord brackets. - -@item -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 -@lilypond[verbatim,quote,ragged-right] -tonic=fis' -{ <\tonic \transpose c g \tonic> } -@end lilypond -@noindent -now works as expected. One can use @code{#@{@dots{}#@}} for -constructing chord constituents. @code{\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. +A new command @code{\temporary} can be applied to overrides in +order to not have them replace previous property settings. If a +@code{\revert} is applied to the same property subsequently, the +previous setting reappears: -@item -@code{\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: - -@lilypond[verbatim,quote,ragged-right,relative=2] -<\tweak Accidental #'color #red cis4 - \tweak Accidental #'color #green es - g> +@lilypond[quote,verbatim,relative=2] +\override NoteHead.color = #red c4 +\override NoteHead.color = #green d +\revert NoteHead.color e2 +\override NoteHead.color = #red c4 +\temporary\override NoteHead.color = #green d +\revert NoteHead.color e +\revert NoteHead.color c @end lilypond -@item -Scheme expressions inside of embedded Lilypond (@code{#@{@dots{}#@}}) -are now executed in lexical closure of the surrounding Scheme code. -@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 @code{ly:export} could previously be used. -@code{ly:export} has been removed. As a consequence, @code{#} 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 @q{splicing} operators @code{$@@} -and @code{#@@} for interpreting the members of a list individually. +This is mainly useful for writing music functions that need to +have some property changed just for the duration of the function. @item -To reduce the necessity for using @code{$}, Scheme expressions written -with @code{#} are interpreted as music inside of music lists, and as -markups or markup lists inside of markups. +@code{\tag}, @code{\removeWithTag}, and @code{\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 @code{\keepWithTag} since one +cannot achieve the same effect by using multiple consecutive +@code{\keepWithTag} commands. @item -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. -@ruser{Customizing chord names} for more information. +The @samp{-d old-relative} option has been removed. Not actually +accessible from the command line any more, its remaining use was +for interpretating @code{\relative} in LilyPond files converted +automatically from version@tie{}1.8 or older. It is unclear how +much of this was actually still operative. @item -The @code{\markuplines} command has been renamed to @code{\markuplist} -for a better match with its semantics and general Lilypond -nomenclature. +The meaning of @code{instrumentTransposition} has been reversed. +After +@example +\set instrumentTransposition = #@{ b #@} +@end example +a written @code{c'} now sounds like @code{b}. Previously, this +would have been the other way round. This and the following change +should make dealing with transposing instruments more +straightforward. @item -The interface for specifying string tunings in tablature has been -simplified considerably and employs the scheme function -@code{\stringTuning} for most purposes. +The music generated by @code{\set} and @code{\override} commands +is no longer affected by @code{\transpose}. The main consequence +is that @code{\transpose} will transpose audible/@/concert pitch and +printed pitch by the same amount even when the transposed music +contains @code{\transposition}. Previously, +@example +\transpose c' f' \transposition bes' +@end example +was equivalent to @code{\transposition f'}. Now it stays +equivalent to @code{\transposition bes'}. @item -Beams can now have their slopes preserved over line breaks. -@lilypond[fragment,quote,relative=2] -\override Beam #'breakable = ##t -a8[ b c d e f g \bar "" \break f e d c b a] -\once \override Beam #'positions = #beam::align-with-broken-parts -a8[ b c d e f g \bar "" \break f e d c b a] -\once \override Beam #'positions = #beam::slope-like-broken-parts -a8[ b c d e f g \bar "" \break f e d c b a] +Tuplets are now created with the @code{\tuplet} command, which +takes a fraction @code{@var{t}/@var{n}} to specify that @var{t} +notes are played in the time usually allowed for @var{n}. One +@code{\tuplet} command can create several tuplet groups if their +duration is typed after the fraction. +@lilypond[quote,verbatim,relative=2] +\tuplet 3/2 { c8 d e } \tuplet 3/2 { f e d } c2 +\tuplet 3/2 4 { c8 d e f e d } c2 @end lilypond -To do this, several callback functions are now deprecated. -@itemize -@item @code{ly:beam::calc-least-squares-positions} -@item @code{ly:beam::slope-damping} -@item @code{ly:beam::shift-region-to-valid} -@end itemize -Furthermore, @code{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 @code{positions} parameter. +The @code{\times} command with its inverted fraction order +@code{@var{n}/@var{t}} is still available. @item -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 @code{-3} as a number or a fingering event. +Introducing two new markup-commands; @code{\draw-dashed-line} and +@code{\draw-dotted-line}. -@item -Music functions (and their close relatives) can now be defined with -optional arguments. - -@item -For defining commands executed only for their side-effects, -@code{define-void-function} is now available. - -@item -There is a new @code{define-event-function} command in analogy to -@code{define-music-function} that can be used for defining music -functions acting as post events without requiring a direction specifier -(@code{-}, @code{^}, or @code{_}) placed before them. -@lilypond[quote,verbatim,ragged-right] -dyn=#(define-event-function (parser location arg) (markup?) - (make-dynamic-script arg)) -\relative c' { c\dyn pfsss } -@end lilypond +@noindent +The dashed-line extends to the whole length given by @var{dest}, if +@code{full-length} is set to @code{#t} (this is the default) without any +space at the beginning or end. @code{off} will then be altered to fit. +To insist on the given (or default) values of @code{on}, @code{off} use +@code{\override #'(full-length . #f)}. Manual settings for @code{on}, +@code{off} and @code{phase} are possible. -@item -A list of ASCII aliases for special characters can be included. -@lilypond[quote,verbatim] -\paper { - #(include-special-characters) +@noindent +The dotted-line always extends to the whole length given by @var{dest}, +without any space at the beginning or end. Manual settings for +@code{off} are possible to get larger or smaller space between the dots. +The given (or default) value of @code{off} will be altered to fit the +line-length. + +@lilypond[verbatim,quote] +\markup { + \draw-dashed-line #'(5.1 . 2.3) + \override #'(on . 0.3) + \override #'(off . 0.5) + \draw-dashed-line #'(5.1 . 2.3) + \draw-dotted-line #'(5.1 . 2.3) + \override #'(thickness . 2) + \override #'(off . 0.2) + \draw-dotted-line #'(5.1 . 2.3) } -\markup "• † ©right; &OE; &ss; ¶" @end lilypond @item -There is a new @code{define-scheme-function} command in analogy to -@code{define-music-function} that can be used to define functions -evaluating to Scheme expressions while accepting arguments in Lilypond -syntax. - -@item -The construct @code{#@{ @dots{} #@}} 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 @code{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. - -@item -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. - -@item -New command-line option @option{--loglevel=@var{level}} to control how much output -LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG. +Starting with version@tie{}2.17.10, error messages or the +@code{textedit} @acronym{URI} used for point-and-click +functionality specify column numbers starting with@tie{}1 rather +than@tie{}0. The byte offset (also part of @code{textedit} +@acronym{URI}s) still starts at@tie{}0. @item -@code{\once \set} now correctly resets the property value to the previous value. -@lilypond[fragment,quote,relative=2] - \set fingeringOrientations = #'(left) - 4 - \once \set fingeringOrientations = #'(right) - - -"left" +The @code{\clef} command supports optional octavation: +@lilypond[verbatim,quote,relative=1] +\clef "treble_(8)" +c2 c +\clef "bass^[15]" +c2 c @end lilypond @item -The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now -automatically broken if a different direction is explicitly given. -@lilypond[fragment,quote,relative=2] -c4_\< c c^\> c c1_\p -@end lilypond - - -@item -Appoggiaturas and acciaccaturas now also work inside a slur, not only inside -a phrasing slur. Also, a function @code{\slashedGrace} was added that does -not use a slur from the acciaccatura note. -@lilypond[fragment,quote,relative=2] -c4( \appoggiatura e8 d4 \acciaccatura e8 d4 \slashedGrace e8 c4) -@end lilypond - +The LilyPond syntax of dot-separated words @code{Voice.Accidental} +has been made interchangeable with @code{#'(Voice Accidental)}, a +Scheme list of symbols. As one result, code like +@example +\override Voice.TextSpanner #'(bound-details left text) = "rit." +@end example +is now equivalent to +@example +\override Voice.TextSpanner bound-details.left.text = "rit." +@end example +or even +@example +\override #'(Voice TextSpanner) bound-details.left.text = "rit." +@end example @item -To suppress the line on a crescendo text spanner (and other similar spanners), -LilyPond now fully supports the @code{#'style = #'none} property. -@lilypond[fragment,quote,relative=2] -\override DynamicTextSpanner #'style = #'none -c4\cresc c c g, c'\p +Grob and grob property path no longer need to be specified as two +separate arguments to commands like @samp{\override} and +@code{\revert}, allowing for the syntax +@example +\override Voice.TextSpanner.bound-details.left.text = "rit." +@end example +Since complementary music functions like @samp{\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 @samp{\override} and @samp{\revert} for +compatibility reasons, is deprecated. + +@item +Due to words now being accepted as symbol function arguments, the +interfaces of @samp{\accidentalStyle}, @samp{\alterBroken}, +@samp{\footnote} and @samp{\tweak} had to be redesigned where +optional symbol arguments were involved. Please check the +respective music function documentation for details. + +@item +Several commands now accept symbol lists (conveniently entered as +dot-separated words) for various kinds of arguments. These +include @samp{\accidentalStyle}, @samp{\alterBroken}, +@samp{\footnote}, @samp{\hide}, @samp{\omit}, +@samp{\overrideProperty}, @samp{\shape}, and @samp{\tweak}. + +@item +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 @code{.|:}. The command @code{\defineBarLine} provides an easy way +to define additional bar line styles. + +@item +Accidentals in the key signature may be printed in octaves other +than their traditional positions, or in multiple octaves. +@lilypond[quote,relative=0] +\override Staff.KeySignature #'flat-positions = #'((-5 . 5)) +\override Staff.KeyCancellation #'flat-positions = #'((-5 . 5)) +\clef bass \key es\major es g bes d +\clef treble \bar "||" \key es\major es g bes d +\override Staff.KeySignature #'sharp-positions = #'(2) +\bar "||" \key d\major b fis b2 @end lilypond -@item -LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz! - -@item -Glissandi can now span multiple lines. - @end itemize @ifhtml For older news, go to +@uref{http://lilypond.org/doc/v2.16/Documentation/changes/}, @uref{http://lilypond.org/doc/v2.14/Documentation/changes/}, -@uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html}, or @uref{../,go back} to the Documentation index.