1 \input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
2 @setfilename lilypond-changes.info
3 @settitle LilyPond Changes
8 @macro inputfileref{DIR,NAME}
9 @uref{../../\DIR\/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
11 @macro usermanref{NAME}
12 @inforef{\NAME\,,../user/lilypond/lilypond}@c
17 @macro inputfileref{DIR,NAME}
20 @macro usermanref{NAME}
21 See user manual, \NAME\
25 @macro textanchor{NAME}
32 @documentencoding UTF-8
39 @top New features in 2.20 since 2.18
41 @allowcodebreaks false
49 * add new items at the top
51 * only show verbatim input for syntax/input changes
53 * try to be as brief possible in those cases
55 * don't try to provide real-world examples, they often get too big,
56 which scares away people.
58 * Write complete sentences.
60 * only show user-visible changes.
65 A new @code{output-attributes} grob property is now used for svg output
66 instead of the @code{id} grob property. It allows multiple attributes
67 to be defined as an association list. For example, @code{#'((id . 123)
68 (class . foo) (data-whatever . @qq{bar}))} will produce the following
69 group tag in an SVG file: @code{<g id=@qq{123} class=@qq{foo}
70 data-whatever=@qq{bar}> @dots{} </g>}.
73 Slurs and phrasing slurs may now be started from individual notes
74 in a chord. Several simultanous slurs per @code{Voice} need to be
75 distinguished by @code{spanner-id} setting.
78 The music and grob property @code{spanner-id} for distinguishing
79 simultaneous slurs and phrasing slurs has been changed from a
80 string to a @q{key}, a non-negative integer or symbol.
83 There is a new command @code{\=} for specifying the
84 @code{spanner-id} for simultaneous slurs and phrasing slurs.
85 @lilypond[verbatim,quote]
87 <c~ f\=1( g\=2( >2 <c e\=1) a\=2) >
92 Blocks introduced with @code{\header} can be stored in variables
93 and used as arguments to music and scheme functions and as the
94 body of @code{#@{@dots{}#@}} constructs. They are represented as
97 While @code{\book}, @code{\bookpart}, @code{\score}, @code{\with},
98 @code{\layout}, @code{\midi}, @code{\paper} blocks can be passed
99 around in similar manner, they are represented by different data
103 Dot-separated symbol lists like @code{FretBoard.stencil} were
104 already supported as of version@tie{}2.18. They may now also
105 contain unsigned integers, and may alternatively be separated by
106 commata. This allows usage such as
107 @lilypond[quote,verbatim]
108 { \time 2,2,1 5/8 g'8 8 8 8 8 }
112 \tagGroup violin,oboe,bassoon
116 Such lists may also be used in expressions for assignments, sets,
117 and overrides. This allows usage such as
118 @lilypond[quote,verbatim]
119 { \unset Timing.beamExceptions
120 \set Timing.beatStructure = 1,2,1
125 Association list elements could previously be assigned values
126 individually (for example, paper variables like
127 @code{system-system-spacing.basic-distance}). They may now be
128 also referenced in this manner, as with
131 \void \displayScheme \system-system-spacing.basic-distance
135 In combination with the previously mentioned changes, this allows
136 setting and referencing pseudovariables like @code{violin.1}.
139 LilyPond source files may now be embedded inside the generated PDF files.
140 This experimental feature is disabled by default and may be regarded as unsafe,
141 as PDF documents with hidden content tend to present a security risk.
142 Please note that not all PDF viewers have the ability to handle embedded
143 documents (if not, the PDF output will appear normally and source files
144 will remain invisible). This feature only works with the PDF backend.
147 French note names are now defined specifically instead of
148 being aliased to Italian note names: in addition to the
149 generic Italian-derived syntax, the @var{d} pitch may be
150 entered as @code{ré}. Double sharps may also be
151 entered using the @code{-x} suffix.
154 Additional bass strings (for lute tablature) are supported.
155 @lilypond[quote,verbatim]
156 m = { f'4 d' a f d a, g, fis, e, d, c, \bar "|." }
163 tablatureFormat = #fret-letter-tablature-format
167 stringTunings = \stringTuning <a, d f a d' f'>
168 additionalBassStrings = \stringTuning <c, d, e, fis, g,>
169 fretLabels = #'("a" "b" "r" "d" "e" "f" "g" "h" "i" "k")
176 The markup-list-command @code{\table} is now available.
177 Each column may be aligned differently.
178 @lilypond[quote,verbatim]
180 \override #'(padding . 2)
184 \underline { center-aligned right-aligned center-aligned left-aligned }
185 one "1" thousandth "0.001"
186 eleven "11" hundredth "0.01"
187 twenty "20" tenth "0.1"
188 thousand "1000" one "1.0"
194 A new markup-command, @code{\with-dimensions-from}, makes
195 @code{\with-dimensions} easier to use by taking the new
196 dimensions from a markup object, given as first argument.
197 @lilypond[quote,verbatim]
199 \pattern #5 #Y #0 "x"
200 \pattern #5 #Y #0 \with-dimensions-from "x" "f"
201 \pattern #5 #Y #0 \with-dimensions-from "x" "g"
202 \override #'(baseline-skip . 2)
204 \pattern #5 #X #0 "n"
205 \pattern #5 #X #0 \with-dimensions-from "n" "m"
206 \pattern #5 #X #0 \with-dimensions-from "n" "!"
212 A new page breaking function @code{ly:one-line-auto-height-breaking}
213 places a whole score on a single line and changes the page width
214 to match, just like @code{ly:one-line-breaking}. The difference is that
215 it also automatically modifies the height of the page to fit the height
219 Markup-command @code{\draw-squiggle-line} is now available.
220 Customizing is possible with overrides of @code{thickness}, @code{angularity},
221 @code{height} and @code{orientation}
222 @lilypond[quote,verbatim]
225 \draw-squiggle-line #0.5 #'(3 . 3) ##t
228 \override #'(thickness . 4)
229 \draw-squiggle-line #0.5 #'(3 . -3) ##t
232 \override #'(angularity . -5)
233 \draw-squiggle-line #0.5 #'(-3 . -3) ##t
235 \translate #'(3 . -3)
236 \override #'(angularity . 2)
237 \override #'(height . 0.3)
238 \override #'(orientation . -1)
239 \draw-squiggle-line #0.2 #'(-3 . 3) ##t
244 A new command, @code{\RemoveAllEmptyStaves}, has been made available, which
245 acts exactly like @code{\RemoveEmptyStaves}, except for also removing empty
246 staves on the first system in a score.
249 Markup-commands @code{\undertie} and @code{\overtie} are now available, as well
250 as the generic markup-command @code{\tie}.
251 @lilypond[quote,verbatim]
253 \undertie "undertied"
258 c''1 \prall -\tweak text \markup \tie "131" -1
261 { \voiceOne \m \voiceTwo \m }
265 @code{TabStaff} is now able to print micro-tones for bendings etc.
266 @lilypond[quote,verbatim]
270 supportNonIntegerFret = ##t
274 mus = \relative { c'4 cih d dih }
277 \new Staff << \clef "G_8" \mus >>
283 Two new styles of whiteout are now available. The @code{outline} style
284 approximates the contours of a glyph's outline, and its shape is
285 produced from multiple displaced copies of the glyph. The
286 @code{rounded-box} style produces a rounded rectangle shape. For all
287 three styles, including the default @code{box} style, the whiteout
288 shape's @code{thickness}, as a multiple of staff-line thickness, can be
291 @lilypond[verbatim,quote]
294 \filled-box #'(-1 . 15) #'(-3 . 4) #1
295 \override #'(thickness . 3)
296 \whiteout whiteout-box
300 \filled-box #'(-1 . 24) #'(-3 . 4) #1
301 \override #'(style . rounded-box)
302 \override #'(thickness . 3)
303 \whiteout whiteout-rounded-box
307 \filled-box #'(-1 . 18) #'(-3 . 4) #1
308 \override #'(style . outline)
309 \override #'(thickness . 3)
310 \whiteout whiteout-outline
313 \override Staff.Clef.whiteout-style = #'outline
314 \override Staff.Clef.whiteout = 3
320 All of @code{\override}, @code{\revert}, @code{\set}, and
321 @code{\unset} now work with the @code{\once} prefix for making
323 @lilypond[quote,verbatim]
326 \override NoteHead.color = #red
328 \once \override NoteHead.color = #green
330 \once \revert NoteHead.color
332 \revert NoteHead.color
338 When outputting MIDI, LilyPond will now store the @code{title}
339 defined in a score's @code{\header} block (or, if there is no
340 such definition on the @code{\score} level, the first such
341 definition found in a @code{\header} block of the score's
342 enclosing @code{\bookpart}, @code{\book}, or top-level scope)
343 as the name of the MIDI sequence in the MIDI file. Optionally,
344 the name of the MIDI sequence can be overridden using the new
345 @code{midititle} @code{\header} field independently of
346 @code{title} (for example, in case @code{title} contains markup
347 code which does not render as plain text in a satisfactory way
351 Music (and scheme and void) functions and markup commands that
352 just supply the final parameters to a chain of overrides, music
353 function and markup command calls can now be defined in the form
354 of just writing the expression cut short with @code{\etc}.
356 @lilypond[verbatim,quote]
357 bold-red-markup = \markup \bold \with-color #red \etc
358 highlight = \tweak font-size 3 \tweak color #red \etc
360 \markup \bold-red "text"
361 \markuplist \column-lines \bold-red { One Two }
363 { c' \highlight d' e'2-\highlight -! }
367 LilyPond functions defined with @code{define-music-function},
368 @code{define-event-function}, @code{define-scheme-function} and
369 @code{define-void-function} can now be directly called from Scheme
370 as if they were genuine Scheme procedures. Argument checking and
371 matching will still be performed in the same manner as when
372 calling the function through LilyPond input. This includes the
373 insertion of defaults for optional arguments not matching their
374 predicates. Instead of using @code{\default} in the actual
375 argument list for explicitly skipping a sequence of optional
376 arguments, @code{*unspecified*} can be employed.
379 Current input location and parser are now stored in GUILE fluids
380 and can be referenced via the function calls @code{(*location*)}
381 and @code{(*parser*)}. Consequently, a lot of functions
382 previously taking an explicit @code{parser} argument no longer do
385 Functions defined with @code{define-music-function},
386 @code{define-event-function}, @code{define-scheme-function} and
387 @code{define-void-function} no longer use @code{parser} and
388 @code{location} arguments.
390 With those particular definitions, LilyPond will try to recognize
391 legacy use of @code{parser} and @code{location} arguments,
392 providing backwards-compatible semantics for some time.
395 In the "english" notename language, the long notenames for pitches
396 with accidentals now contain a hyphen for better readability. You
401 instead of the previous
406 Double accidentals do not get another hyphen, so the Dutch
407 @code{cisis} has the long English notename @code{c-sharpsharp}.
410 The visual style of tremolo slashes (shape, style and slope)
411 is now more finely controlled.
412 @lilypond[quote,relative=2]
414 \override StemTremolo.shape = #'beam-like
416 \override StemTremolo.style = #'constant
423 Multi-measure rests have length according to their total duration,
424 under the control of @code{MultiMeasureRest.space-increment}.
426 { \compressFullBarRests
427 \override Staff.MultiMeasureRest.space-increment = 3.0
432 Page numbers may now be printed in roman numerals, by setting the
433 @code{page-number-type} paper variable.
436 It is now possible to use @code{\time} and @code{\partial}
437 together to change the time signature in mid measure.
439 @lilypond[verbatim,quote,relative=1]
440 \override Score.BarNumber.break-visibility = #end-of-line-invisible
441 \partial 4 \time 3/4 f4 | 2 4 | 2 \bar "||"
442 \time 9/8 \partial 4. f8 8 8 | 2. 8 8 8 |
446 It is now possible to override the @code{text} property of
449 @lilypond[verbatim,fragment,quote]
451 \new ChordNames \chordmode {
453 \once \override ChordName.text = #"foo"
460 Improved horizontal alignment when using @code{TextScript},
461 with @code{DynamicText} or @code{LyricText}.
464 A new command @code{\magnifyStaff} has been added which scales staff
465 sizes, staff lines, bar lines, beamlets and horizontal spacing generally
466 at the @code{Staff} context level. Staff lines are prevented from being
467 scaled smaller than the default since the thickness of stems, slurs, and
468 the like are all based on the staff line thickness.
471 @code{InstrumentName} now supports @code{text-interface}.
474 There is now support for controlling the @q{expression level} of
475 MIDI channels using the @code{Staff.midiExpression} context property.
476 This can be used to alter the perceived volume of even sustained notes
477 (albeit in a very @q{low-level} way) and accepts a number value between
478 @code{0.0} and @code{1.0}.
483 midiExpression = #0.6
484 midiInstrument = #"clarinet"
489 \set Staff.midiExpression = #0.7 s4\f\<
490 \set Staff.midiExpression = #0.8 s4
491 \set Staff.midiExpression = #0.9 s4
492 \set Staff.midiExpression = #1.0 s4
494 \set Staff.midiExpression = #0.9 s4\>
495 \set Staff.midiExpression = #0.8 s4
496 \set Staff.midiExpression = #0.7 s4
497 \set Staff.midiExpression = #0.6 s4\!
505 Support for making it easier to use alternative @q{music} fonts other
506 than the default Emmentaler in LilyPond has been added. See
507 @uref{http://fonts.openlilylib.org/} for more information.
510 Grobs and their parents can now be aligned separately allowing
511 more flexibility for grob positions. For example the @q{left} edge of a
512 grob can now be aligned on the @q{center} of its parent.
515 Improvements to the @code{\partial} command have been made to
516 avoid problems when using multiple, parallel contexts.
518 @item @code{\chordmode} can now use @code{< >} and @code{<< >>}
522 A new command @code{\tagGroup} has now been added. This complements
523 the existing @code{\keepWithTag} and @code{\removeWithTag} commands.
527 \tagGroup #'(violinI violinII viola cello)
530 declares a list of @q{tags} that belong to a single @q{tag group}.
533 \keepWithTag #'violinI
536 Is now only concerned with @q{tags} from @q{violinI}’s tag group.
538 Any element of the included music tagged with one or more tags from the
539 group, but @emph{not} with @var{violinI}, will be removed.
542 The @code{\addlyrics} function now works with arbitrary contexts
543 incuding @code{Staff}.
546 String numbers can now also be used to print roman numerals
547 (e.g. for unfretted string instruments).
548 @lilypond[verbatim,quote,relative=2]
557 The @code{thin-kern} property of the @code{BarLine} grob has been
558 renamed to @code{segno-kern}.
561 @code{KeyCancellation} grobs now ignore cue clefs (like
562 @code{KeySignature} grobs do).
565 Add support for @code{\once@tie{}\unset}
568 It is now possible to individually color both the dots and parentheses
569 in fret diagrams when using the @code{\fret-diagram-verbose} markup
572 @lilypond[verbatim,quote,relative=1]
575 \override #'(fret-diagram-details . (
576 (finger-code . in-dot))) {
577 \fret-diagram-verbose #'((mute 6)
578 (place-fret 5 3 1 red)
579 (place-fret 4 5 2 inverted)
580 (place-fret 3 5 3 green)
581 (place-fret 2 5 4 blue inverted)
582 (place-fret 1 3 1 violet)
587 \override #'(fret-diagram-details . (
588 (finger-code . below-string))) {
589 \fret-diagram-verbose #'((mute 6)
590 (place-fret 5 3 1 red parenthesized)
591 (place-fret 4 5 2 yellow
594 (place-fret 3 5 3 green)
595 (place-fret 2 5 4 blue )
604 Two new properties have been added for use in
605 @code{fret-diagram-details} when using the @code{\fret-diagram-verbose}
606 markup command; @code{fret-label-horizontal-offset} which affects the
607 @code{fret-label-indication} and @code{paren-padding} which controls the
608 space between the dot and the parentheses surrounding it.
610 @lilypond[verbatim,quote,relative=1]
613 \fret-diagram-verbose #'((mute 6)
617 (place-fret 1 6 4 parenthesized)
622 \override #'(fret-diagram-details . (
623 (fret-label-horizontal-offset . 2)
624 (paren-padding . 0.25))) {
625 \fret-diagram-verbose #'((mute 6)
629 (place-fret 1 6 4 parenthesized)
638 A new markup command @code{\justify-line} has been added. Similar to
639 the @code{\fill-line} markup command except that instead of setting
640 @emph{words} in columns, the @code{\justify-line} command balances the
641 whitespace between them ensuring that when there are three or more
642 words in a markup, the whitespace is always consistent.
644 @lilypond[quote,verbatim,papersize=a6]
645 \markup \fill-line {oooooo oooooo oooooo oooooo}
646 \markup \fill-line {ooooooooo oooooooo oo ooo}
649 @lilypond[quote,verbatim,papersize=a6]
650 \markup \justify-line {oooooo oooooo oooooo oooooo}
651 \markup \justify-line {ooooooooo oooooooo oo ooo}
655 A new command @code{\magnifyMusic} has been added, which allows
656 the notation size to be changed without changing the staff size,
657 while automatically scaling stems, beams, and horizontal spacing.
659 @lilypond[verbatim,quote]
661 \new Voice \relative {
663 <e' e'>4 <f f'>8. <g g'>16 <f f'>8 <e e'>4 r8
665 \new Voice \relative {
668 \override Score.SpacingSpanner.spacing-increment = #(* 1.2 0.63)
669 r32 c'' a c a c a c r c a c a c a c
670 r c a c a c a c a c a c a c a c
677 A new flexible template suitable for a range of choral music, is now
678 provided. This may be used to create simple choral music, with or
679 without piano accompaniment, in two or four staves. Unlike other
680 templates, this template is @q{built-in}, which means it does not
681 need to be copied and edited: instead it is simply @code{\include}'d
682 in the input file. For details, see @rlearning{Built-in templates}.
685 The positioning of tuplet numbers for kneed beams has been significantly
686 improved. Previously, tuplet numbers were placed according to the
687 position of the tuplet bracket, even if it was not printed. This could
688 lead to stranded tuplet numbers. Now they are now positioned
689 closer to the kneed-beam when an appropriate beam segment exists for its
690 placement and when the bracket is not drawn.
692 Collision detection is also added, offsetting horizontally if too close
693 to an adjoining note column but preserving the number's vertical
694 distance from the kneed beam. If the number itself is too large to
695 fit in the available space the original, bracket-based, positioning
696 system is used instead; and in the event of a collision (e.g. with an
697 accidental) the tuplet number is moved vertically away instead.
699 @lilypond[verbatim,fragment,quote,relative=1]
701 \override Beam.auto-knee-gap = 3
710 The original kneed-beam tuplet behavior is still available through an
711 @code{\override} via a new, @code{knee-to-beam} property.
713 @lilypond[verbatim,fragment,quote,relative=1]
715 \override Beam.auto-knee-gap = 3
716 \override TupletNumber.knee-to-beam = ##f
725 @code{\lyricsto} and @code{\addLyrics} have been @q{harmonized}. Both
726 now accept the same kind of delimited argument list that @code{\lyrics}
727 and @code{\chords} accept. Backward compatibility has been added so
728 music identifiers (i.e. @code{\mus}) are permitted as arguments. A
729 @code{convert-ly} rule has been added that removes redundant uses of
730 @code{\lyricmode} and rearranges combinations with context starters such
731 that @code{\lyricsto} in general is applied last (i.e. like
732 @code{\lyricmode} would be).
735 Scheme functions and identifiers can now be used as output definitions.
738 Scheme expressions can now be used as chord constituents.
741 Improved visual spacing of small and regular @q{MI} Funk and Walker
742 noteheads so they are now the same width as other shaped notes in
743 their respective sets. @code{SOL} noteheads are also now visually
744 improved when used with both the normal Aiken and Sacred Harp heads, as
745 well as with the thin variants.
748 @code{LeftEdge} now has a definable @code{Y-extent} (i.e.vertical). See
749 @rinternals{LeftEdge}.
752 Added a new @code{make-path-stencil} function that supports all
753 @code{path} commands both relative and absolute:
755 @code{lineto}, @code{rlineto}, @code{curveto}, @code{rcurveto},
756 @code{moveto}, @code{rmoveto}, @code{closepath}. The function also
757 supports @q{single-letter} syntax used in standard SVG path commands:
759 @code{L}, @code{l}, @code{C}, @code{c}, @code{M}, @code{m}, @code{Z} and
760 @code{z}. The new command is also backward-compatible with the original
761 @code{make-connected-path-stencil} function. Also see
762 @file{scm/stencil.scm}.
765 Context properties named in the @samp{alternativeRestores} property are
766 restored to their value at the start of the @emph{first} alternative in
767 all subsequent alternatives.
769 Currently the default set restores @q{current meter};
771 @lilypond[verbatim,fragment,quote,relative=2]
773 \repeat volta 2 { c2 e4 | }
782 @q{measure position};
784 @lilypond[verbatim,fragment,quote,relative=2]
786 \repeat volta 2 { c2 e4 | }
789 \set Timing.measurePosition = #(ly:make-moment -1/2)
797 and @q{chord changes};
799 @lilypond[verbatim,fragment,quote]
802 \set chordChanges = ##t
803 \chordmode { c1:m d:m c:m d:m }
806 \repeat volta 2 { \chordmode { c1:m } }
808 { \chordmode { d:m } }
809 { \chordmode { c:m } }
817 Improved MIDI output for breathe marks. After tied notes, breaths take
818 time @emph{only} from the last note of the tie; e.g.
819 @code{@{ c4~ c8 \breathe @}} performs as @code{@{ c4~ c16 r @}} instead
820 of @code{@{ c4 r8 @}}. This is more consistent with articulations and
821 how humans interpret breaths after ties. It now also makes it easier to
822 align simultaneous breathe marks over multiple parts, all with different
826 A new note head style for Tabulature has been added;
827 @code{TabNoteHead.style = #'slash}.
830 Four new Clef glyphs have been added @emph{Double G}, @emph{Tenor G},
831 @emph{Varpercussion} and @emph{varC} and their related tessitura.
832 @lilypond[verbatim,quote,fragment]
833 \override Staff.Clef.full-size-change = ##t
836 \clef "tenorG" c c c c
838 \clef "altovarC" c c c c
839 \clef "tenorvarC" c c c c
840 \clef "baritonevarC" c c c c
841 \clef "varpercussion" c c c c
844 \override Staff.Clef.full-size-change = ##f
847 \clef "tenorG" c c c c
849 \clef "altovarC" c c c c
850 \clef "tenorvarC" c c c c
851 \clef "baritonevarC" c c c c
852 \clef "varpercussion" c c c c
856 Isolated durations in music sequences now stand for unpitched
857 notes. This may be useful for specifying rhythms to music or
858 scheme functions. When encountered in the final score, the
859 pitches are provided by the preceding note or chord. Here are two
860 examples where this makes for readable input:
862 @lilypond[verbatim,quote]
863 \new DrumStaff \with { \override StaffSymbol.line-count = 1 }
866 tambourine 8 \tuplet 3/2 { 16 16 16 }
867 8 \tuplet 3/2 { 16 16 16 } 8 8 |
871 @lilypond[verbatim,quote]
872 \new Staff { r16 c'16 ~ 8 ~ 4 ~ 2 | }
876 @code{\displayLilyMusic} and its underlying Scheme functions no
877 longer omit redundant note durations. This makes it easier to
878 reliably recognize and format standalone durations in expressions
885 Beaming exceptions can now be constructed using the
886 @code{\beamExceptions} scheme function. One can now write
888 @lilypond[verbatim,quote,relative=1]
890 \set Timing.beamExceptions =
891 \beamExceptions { 32[ 32] 32[ 32] 32[ 32] }
893 \repeat unfold 6 { c32 } |
897 with multiple exceptions separated with @code{|} bar checks
898 (writing the exception pattern without pitches is convenient but
899 not mandatory). Previously, setting the beam exceptions would
900 have required writing
903 \set Timing.beamExceptions =
905 (end . ;entry for end of beams
906 ( ;start of alist of end points
907 ((1 . 32) . (2 2 2)) ;rule for 1/32 beams -- end each 1/16
912 The most common articulations are now reflected in MIDI output.
913 Accent and marcato make notes louder; staccato, staccatissimo and
914 portato make them shorter. Breath marks shorten the previous
917 This behavior is customizable through the @code{midiLength} and
918 @code{midiExtraVelocity} properties on @code{ArticulationEvent}.
919 See @file{script-init.ly} for examples.
922 The PostScript functionality of stroke adjustment is no longer
923 applied automatically but left to the discretion of the PostScript
924 device (by default, Ghostscript uses it for resolutions up to
925 150dpi when generating raster images). When it is enabled, a more
926 complex drawing algorithm designed to benefit from stroke
927 adjustment is employed mostly for stems and bar lines.
929 Stroke adjustment can be forced by specifying the command line
930 option @samp{-dstrokeadjust} to LilyPond. When generating
931 @code{PDF} files, this will usually result in markedly better
932 looking @code{PDF} previews but significantly larger file size.
933 Print quality at high resolutions will be unaffected.
938 For older news, go to
939 @uref{http://lilypond.org/doc/v2.18/Documentation/changes/},
940 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/},
941 or @uref{../,go back} to the Documentation index.