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 Slurs and phrasing slurs may now be started from individual notes
66 in a chord. Several simultanous slurs per @code{Voice} need to be
67 distinguished by @code{spanner-id} setting.
70 The music and grob property @code{spanner-id} for distinguishing
71 simultaneous slurs and phrasing slurs has been changed from a
72 string to a @q{key}, a non-negative integer or symbol.
75 There is a new command @code{\=} for specifying the
76 @code{spanner-id} for simultaneous slurs and phrasing slurs.
77 @lilypond[verbatim,quote]
79 <c~ f\=1( g\=2( >2 <c e\=1) a\=2) >
84 Blocks introduced with @code{\header} can be stored in variables
85 and used as arguments to music and scheme functions and as the
86 body of @code{#@{@dots{}#@}} constructs. They are represented as
89 While @code{\book}, @code{\bookpart}, @code{\score}, @code{\with},
90 @code{\layout}, @code{\midi}, @code{\paper} blocks can be passed
91 around in similar manner, they are represented by different data
95 Dot-separated symbol lists like @code{FretBoard.stencil} were
96 already supported as of version@tie{}2.18. They may now also
97 contain unsigned integers, and may alternatively be separated by
98 commata. This allows usage such as
99 @lilypond[quote,verbatim]
100 { \time 2,2,1 5/8 g'8 8 8 8 8 }
104 \tagGroup violin,oboe,bassoon
108 Such lists may also be used in expressions for assignments, sets,
109 and overrides. This allows usage such as
110 @lilypond[quote,verbatim]
111 { \unset Timing.beamExceptions
112 \set Timing.beatStructure = 1,2,1
117 Association list elements could previously be assigned values
118 individually (for example, paper variables like
119 @code{system-system-spacing.basic-distance}). They may now be
120 also referenced in this manner, as with
123 \void \displayScheme \system-system-spacing.basic-distance
127 In combination with the previously mentioned changes, this allows
128 setting and referencing pseudovariables like @code{violin.1}.
131 LilyPond source files may now be embedded inside the generated PDF files.
132 This experimental feature is disabled by default and may be regarded as unsafe,
133 as PDF documents with hidden content tend to present a security risk.
134 Please note that not all PDF viewers have the ability to handle embedded
135 documents (if not, the PDF output will appear normally and source files
136 will remain invisible). This feature only works with the PDF backend.
139 French note names are now defined specifically instead of
140 being aliased to Italian note names: in addition to the
141 generic Italian-derived syntax, the @var{d} pitch may be
142 entered as @code{ré}. Double sharps may also be
143 entered using the @code{-x} suffix.
146 Additional bass strings (for lute tablature) are supported.
147 @lilypond[quote,verbatim]
148 m = { f'4 d' a f d a, g, fis, e, d, c, \bar "|." }
155 tablatureFormat = #fret-letter-tablature-format
159 stringTunings = \stringTuning <a, d f a d' f'>
160 additionalBassStrings = \stringTuning <c, d, e, fis, g,>
161 fretLabels = #'("a" "b" "r" "d" "e" "f" "g" "h" "i" "k")
168 The markup-list-command @code{\table} is now available.
169 Each column may be aligned differently.
170 @lilypond[quote,verbatim]
172 \override #'(padding . 2)
176 \underline { center-aligned right-aligned center-aligned left-aligned }
177 one "1" thousandth "0.001"
178 eleven "11" hundredth "0.01"
179 twenty "20" tenth "0.1"
180 thousand "1000" one "1.0"
186 A new markup-command, @code{\with-dimensions-from}, makes
187 @code{\with-dimensions} easier to use by taking the new
188 dimensions from a markup object, given as first argument.
189 @lilypond[quote,verbatim]
191 \pattern #5 #Y #0 "x"
192 \pattern #5 #Y #0 \with-dimensions-from "x" "f"
193 \pattern #5 #Y #0 \with-dimensions-from "x" "g"
194 \override #'(baseline-skip . 2)
196 \pattern #5 #X #0 "n"
197 \pattern #5 #X #0 \with-dimensions-from "n" "m"
198 \pattern #5 #X #0 \with-dimensions-from "n" "!"
204 A new page breaking function @code{ly:one-line-auto-height-breaking}
205 places a whole score on a single line and changes the page width
206 to match, just like @code{ly:one-line-breaking}. The difference is that
207 it also automatically modifies the height of the page to fit the height
211 Markup-command @code{\draw-squiggle-line} is now available.
212 Customizing is possible with overrides of @code{thickness}, @code{angularity},
213 @code{height} and @code{orientation}
214 @lilypond[quote,verbatim]
217 \draw-squiggle-line #0.5 #'(3 . 3) ##t
220 \override #'(thickness . 4)
221 \draw-squiggle-line #0.5 #'(3 . -3) ##t
224 \override #'(angularity . -5)
225 \draw-squiggle-line #0.5 #'(-3 . -3) ##t
227 \translate #'(3 . -3)
228 \override #'(angularity . 2)
229 \override #'(height . 0.3)
230 \override #'(orientation . -1)
231 \draw-squiggle-line #0.2 #'(-3 . 3) ##t
236 A new command, @code{\RemoveAllEmptyStaves}, has been made available, which
237 acts exactly like @code{\RemoveEmptyStaves}, except for also removing empty
238 staves on the first system in a score.
241 Markup-commands @code{\undertie} and @code{\overtie} are now available, as well
242 as the generic markup-command @code{\tie}.
243 @lilypond[quote,verbatim]
245 \undertie "undertied"
250 c''1 \prall -\tweak text \markup \tie "131" -1
253 { \voiceOne \m \voiceTwo \m }
257 @code{TabStaff} is now able to print micro-tones for bendings etc.
258 @lilypond[quote,verbatim]
262 supportNonIntegerFret = ##t
266 mus = \relative { c'4 cih d dih }
269 \new Staff << \clef "G_8" \mus >>
275 Two new styles of whiteout are now available. The @code{outline} style
276 approximates the contours of a glyph's outline, and its shape is
277 produced from multiple displaced copies of the glyph. The
278 @code{rounded-box} style produces a rounded rectangle shape. For all
279 three styles, including the default @code{box} style, the whiteout
280 shape's @code{thickness}, as a multiple of staff-line thickness, can be
283 @lilypond[verbatim,quote]
286 \filled-box #'(-1 . 15) #'(-3 . 4) #1
287 \override #'(thickness . 3)
288 \whiteout whiteout-box
292 \filled-box #'(-1 . 24) #'(-3 . 4) #1
293 \override #'(style . rounded-box)
294 \override #'(thickness . 3)
295 \whiteout whiteout-rounded-box
299 \filled-box #'(-1 . 18) #'(-3 . 4) #1
300 \override #'(style . outline)
301 \override #'(thickness . 3)
302 \whiteout whiteout-outline
305 \override Staff.Clef.whiteout-style = #'outline
306 \override Staff.Clef.whiteout = 3
312 All of @code{\override}, @code{\revert}, @code{\set}, and
313 @code{\unset} now work with the @code{\once} prefix for making
315 @lilypond[quote,verbatim]
318 \override NoteHead.color = #red
320 \once \override NoteHead.color = #green
322 \once \revert NoteHead.color
324 \revert NoteHead.color
330 When outputting MIDI, LilyPond will now store the @code{title}
331 defined in a score's @code{\header} block (or, if there is no
332 such definition on the @code{\score} level, the first such
333 definition found in a @code{\header} block of the score's
334 enclosing @code{\bookpart}, @code{\book}, or top-level scope)
335 as the name of the MIDI sequence in the MIDI file. Optionally,
336 the name of the MIDI sequence can be overridden using the new
337 @code{midititle} @code{\header} field independently of
338 @code{title} (for example, in case @code{title} contains markup
339 code which does not render as plain text in a satisfactory way
343 Music (and scheme and void) functions and markup commands that
344 just supply the final parameters to a chain of overrides, music
345 function and markup command calls can now be defined in the form
346 of just writing the expression cut short with @code{\etc}.
348 @lilypond[verbatim,quote]
349 bold-red-markup = \markup \bold \with-color #red \etc
350 highlight = \tweak font-size 3 \tweak color #red \etc
352 \markup \bold-red "text"
353 \markuplist \column-lines \bold-red { One Two }
355 { c' \highlight d' e'2-\highlight -! }
359 LilyPond functions defined with @code{define-music-function},
360 @code{define-event-function}, @code{define-scheme-function} and
361 @code{define-void-function} can now be directly called from Scheme
362 as if they were genuine Scheme procedures. Argument checking and
363 matching will still be performed in the same manner as when
364 calling the function through LilyPond input. This includes the
365 insertion of defaults for optional arguments not matching their
366 predicates. Instead of using @code{\default} in the actual
367 argument list for explicitly skipping a sequence of optional
368 arguments, @code{*unspecified*} can be employed.
371 Current input location and parser are now stored in GUILE fluids
372 and can be referenced via the function calls @code{(*location*)}
373 and @code{(*parser*)}. Consequently, a lot of functions
374 previously taking an explicit @code{parser} argument no longer do
377 Functions defined with @code{define-music-function},
378 @code{define-event-function}, @code{define-scheme-function} and
379 @code{define-void-function} no longer use @code{parser} and
380 @code{location} arguments.
382 With those particular definitions, LilyPond will try to recognize
383 legacy use of @code{parser} and @code{location} arguments,
384 providing backwards-compatible semantics for some time.
387 In the "english" notename language, the long notenames for pitches
388 with accidentals now contain a hyphen for better readability. You
393 instead of the previous
398 Double accidentals do not get another hyphen, so the Dutch
399 @code{cisis} has the long English notename @code{c-sharpsharp}.
402 The visual style of tremolo slashes (shape, style and slope)
403 is now more finely controlled.
404 @lilypond[quote,relative=2]
406 \override StemTremolo.shape = #'beam-like
408 \override StemTremolo.style = #'constant
415 Multi-measure rests have length according to their total duration,
416 under the control of @code{MultiMeasureRest.space-increment}.
418 { \compressFullBarRests
419 \override Staff.MultiMeasureRest.space-increment = 3.0
424 Page numbers may now be printed in roman numerals, by setting the
425 @code{page-number-type} paper variable.
428 It is now possible to use @code{\time} and @code{\partial}
429 together to change the time signature in mid measure.
431 @lilypond[verbatim,quote,relative=1]
432 \override Score.BarNumber.break-visibility = #end-of-line-invisible
433 \partial 4 \time 3/4 f4 | 2 4 | 2 \bar "||"
434 \time 9/8 \partial 4. f8 8 8 | 2. 8 8 8 |
438 It is now possible to override the @code{text} property of
441 @lilypond[verbatim,fragment,quote]
443 \new ChordNames \chordmode {
445 \once \override ChordName.text = #"foo"
452 Improved horizontal alignment when using @code{TextScript},
453 with @code{DynamicText} or @code{LyricText}.
456 A new command @code{\magnifyStaff} has been added which scales staff
457 sizes, staff lines, bar lines, beamlets and horizontal spacing generally
458 at the @code{Staff} context level. Staff lines are prevented from being
459 scaled smaller than the default since the thickness of stems, slurs, and
460 the like are all based on the staff line thickness.
463 @code{InstrumentName} now supports @code{text-interface}.
466 There is now support for controlling the @q{expression level} of
467 MIDI channels using the @code{Staff.midiExpression} context property.
468 This can be used to alter the perceived volume of even sustained notes
469 (albeit in a very @q{low-level} way) and accepts a number value between
470 @code{0.0} and @code{1.0}.
475 midiExpression = #0.6
476 midiInstrument = #"clarinet"
481 \set Staff.midiExpression = #0.7 s4\f\<
482 \set Staff.midiExpression = #0.8 s4
483 \set Staff.midiExpression = #0.9 s4
484 \set Staff.midiExpression = #1.0 s4
486 \set Staff.midiExpression = #0.9 s4\>
487 \set Staff.midiExpression = #0.8 s4
488 \set Staff.midiExpression = #0.7 s4
489 \set Staff.midiExpression = #0.6 s4\!
497 Support for making it easier to use alternative @q{music} fonts other
498 than the default Emmentaler in LilyPond has been added. See
499 @uref{http://fonts.openlilylib.org/} for more information.
502 Grobs and their parents can now be aligned separately allowing
503 more flexibility for grob positions. For example the @q{left} edge of a
504 grob can now be aligned on the @q{center} of its parent.
507 Improvements to the @code{\partial} command have been made to
508 avoid problems when using multiple, parallel contexts.
510 @item @code{\chordmode} can now use @code{< >} and @code{<< >>}
514 A new command @code{\tagGroup} has now been added. This complements
515 the existing @code{\keepWithTag} and @code{\removeWithTag} commands.
519 \tagGroup #'(violinI violinII viola cello)
522 declares a list of @q{tags} that belong to a single @q{tag group}.
525 \keepWithTag #'violinI
528 Is now only concerned with @q{tags} from @q{violinI}’s tag group.
530 Any element of the included music tagged with one or more tags from the
531 group, but @emph{not} with @var{violinI}, will be removed.
534 The @code{\addlyrics} function now works with arbitrary contexts
535 incuding @code{Staff}.
538 String numbers can now also be used to print roman numerals
539 (e.g. for unfretted string instruments).
540 @lilypond[verbatim,quote,relative=2]
549 The @code{thin-kern} property of the @code{BarLine} grob has been
550 renamed to @code{segno-kern}.
553 @code{KeyCancellation} grobs now ignore cue clefs (like
554 @code{KeySignature} grobs do).
557 Add support for @code{\once@tie{}\unset}
560 It is now possible to individually color both the dots and parentheses
561 in fret diagrams when using the @code{\fret-diagram-verbose} markup
564 @lilypond[verbatim,quote,relative=1]
567 \override #'(fret-diagram-details . (
568 (finger-code . in-dot))) {
569 \fret-diagram-verbose #'((mute 6)
570 (place-fret 5 3 1 red)
571 (place-fret 4 5 2 inverted)
572 (place-fret 3 5 3 green)
573 (place-fret 2 5 4 blue inverted)
574 (place-fret 1 3 1 violet)
579 \override #'(fret-diagram-details . (
580 (finger-code . below-string))) {
581 \fret-diagram-verbose #'((mute 6)
582 (place-fret 5 3 1 red parenthesized)
583 (place-fret 4 5 2 yellow
586 (place-fret 3 5 3 green)
587 (place-fret 2 5 4 blue )
596 Two new properties have been added for use in
597 @code{fret-diagram-details} when using the @code{\fret-diagram-verbose}
598 markup command; @code{fret-label-horizontal-offset} which affects the
599 @code{fret-label-indication} and @code{paren-padding} which controls the
600 space between the dot and the parentheses surrounding it.
602 @lilypond[verbatim,quote,relative=1]
605 \fret-diagram-verbose #'((mute 6)
609 (place-fret 1 6 4 parenthesized)
614 \override #'(fret-diagram-details . (
615 (fret-label-horizontal-offset . 2)
616 (paren-padding . 0.25))) {
617 \fret-diagram-verbose #'((mute 6)
621 (place-fret 1 6 4 parenthesized)
630 A new markup command @code{\justify-line} has been added. Similar to
631 the @code{\fill-line} markup command except that instead of setting
632 @emph{words} in columns, the @code{\justify-line} command balances the
633 whitespace between them ensuring that when there are three or more
634 words in a markup, the whitespace is always consistent.
636 @lilypond[quote,verbatim,papersize=a6]
637 \markup \fill-line {oooooo oooooo oooooo oooooo}
638 \markup \fill-line {ooooooooo oooooooo oo ooo}
641 @lilypond[quote,verbatim,papersize=a6]
642 \markup \justify-line {oooooo oooooo oooooo oooooo}
643 \markup \justify-line {ooooooooo oooooooo oo ooo}
647 A new command @code{\magnifyMusic} has been added, which allows
648 the notation size to be changed without changing the staff size,
649 while automatically scaling stems, beams, and horizontal spacing.
651 @lilypond[verbatim,quote]
653 \new Voice \relative {
655 <e' e'>4 <f f'>8. <g g'>16 <f f'>8 <e e'>4 r8
657 \new Voice \relative {
660 \override Score.SpacingSpanner.spacing-increment = #(* 1.2 0.63)
661 r32 c'' a c a c a c r c a c a c a c
662 r c a c a c a c a c a c a c a c
669 A new flexible template suitable for a range of choral music, is now
670 provided. This may be used to create simple choral music, with or
671 without piano accompaniment, in two or four staves. Unlike other
672 templates, this template is @q{built-in}, which means it does not
673 need to be copied and edited: instead it is simply @code{\include}'d
674 in the input file. For details, see @rlearning{Built-in templates}.
677 The positioning of tuplet numbers for kneed beams has been significantly
678 improved. Previously, tuplet numbers were placed according to the
679 position of the tuplet bracket, even if it was not printed. This could
680 lead to stranded tuplet numbers. Now they are now positioned
681 closer to the kneed-beam when an appropriate beam segment exists for its
682 placement and when the bracket is not drawn.
684 Collision detection is also added, offsetting horizontally if too close
685 to an adjoining note column but preserving the number's vertical
686 distance from the kneed beam. If the number itself is too large to
687 fit in the available space the original, bracket-based, positioning
688 system is used instead; and in the event of a collision (e.g. with an
689 accidental) the tuplet number is moved vertically away instead.
691 @lilypond[verbatim,fragment,quote,relative=1]
693 \override Beam.auto-knee-gap = 3
702 The original kneed-beam tuplet behavior is still available through an
703 @code{\override} via a new, @code{knee-to-beam} property.
705 @lilypond[verbatim,fragment,quote,relative=1]
707 \override Beam.auto-knee-gap = 3
708 \override TupletNumber.knee-to-beam = ##f
717 @code{\lyricsto} and @code{\addLyrics} have been @q{harmonized}. Both
718 now accept the same kind of delimited argument list that @code{\lyrics}
719 and @code{\chords} accept. Backward compatibility has been added so
720 music identifiers (i.e. @code{\mus}) are permitted as arguments. A
721 @code{convert-ly} rule has been added that removes redundant uses of
722 @code{\lyricmode} and rearranges combinations with context starters such
723 that @code{\lyricsto} in general is applied last (i.e. like
724 @code{\lyricmode} would be).
727 Scheme functions and identifiers can now be used as output definitions.
730 Scheme expressions can now be used as chord constituents.
733 Improved visual spacing of small and regular @q{MI} Funk and Walker
734 noteheads so they are now the same width as other shaped notes in
735 their respective sets. @code{SOL} noteheads are also now visually
736 improved when used with both the normal Aiken and Sacred Harp heads, as
737 well as with the thin variants.
740 @code{LeftEdge} now has a definable @code{Y-extent} (i.e.vertical). See
741 @rinternals{LeftEdge}.
744 Added a new @code{make-path-stencil} function that supports all
745 @code{path} commands both relative and absolute:
747 @code{lineto}, @code{rlineto}, @code{curveto}, @code{rcurveto},
748 @code{moveto}, @code{rmoveto}, @code{closepath}. The function also
749 supports @q{single-letter} syntax used in standard SVG path commands:
751 @code{L}, @code{l}, @code{C}, @code{c}, @code{M}, @code{m}, @code{Z} and
752 @code{z}. The new command is also backward-compatible with the original
753 @code{make-connected-path-stencil} function. Also see
754 @file{scm/stencil.scm}.
757 Context properties named in the @samp{alternativeRestores} property are
758 restored to their value at the start of the @emph{first} alternative in
759 all subsequent alternatives.
761 Currently the default set restores @q{current meter};
763 @lilypond[verbatim,fragment,quote,relative=2]
765 \repeat volta 2 { c2 e4 | }
774 @q{measure position};
776 @lilypond[verbatim,fragment,quote,relative=2]
778 \repeat volta 2 { c2 e4 | }
781 \set Timing.measurePosition = #(ly:make-moment -1/2)
789 and @q{chord changes};
791 @lilypond[verbatim,fragment,quote]
794 \set chordChanges = ##t
795 \chordmode { c1:m d:m c:m d:m }
798 \repeat volta 2 { \chordmode { c1:m } }
800 { \chordmode { d:m } }
801 { \chordmode { c:m } }
809 Improved MIDI output for breathe marks. After tied notes, breaths take
810 time @emph{only} from the last note of the tie; e.g.
811 @code{@{ c4~ c8 \breathe @}} performs as @code{@{ c4~ c16 r @}} instead
812 of @code{@{ c4 r8 @}}. This is more consistent with articulations and
813 how humans interpret breaths after ties. It now also makes it easier to
814 align simultaneous breathe marks over multiple parts, all with different
818 A new note head style for Tabulature has been added;
819 @code{TabNoteHead.style = #'slash}.
822 Four new Clef glyphs have been added @emph{Double G}, @emph{Tenor G},
823 @emph{Varpercussion} and @emph{varC} and their related tessitura.
824 @lilypond[verbatim,quote,fragment]
825 \override Staff.Clef.full-size-change = ##t
828 \clef "tenorG" c c c c
830 \clef "altovarC" c c c c
831 \clef "tenorvarC" c c c c
832 \clef "baritonevarC" c c c c
833 \clef "varpercussion" c c c c
836 \override Staff.Clef.full-size-change = ##f
839 \clef "tenorG" c c c c
841 \clef "altovarC" c c c c
842 \clef "tenorvarC" c c c c
843 \clef "baritonevarC" c c c c
844 \clef "varpercussion" c c c c
848 Isolated durations in music sequences now stand for unpitched
849 notes. This may be useful for specifying rhythms to music or
850 scheme functions. When encountered in the final score, the
851 pitches are provided by the preceding note or chord. Here are two
852 examples where this makes for readable input:
854 @lilypond[verbatim,quote]
855 \new DrumStaff \with { \override StaffSymbol.line-count = 1 }
858 tambourine 8 \tuplet 3/2 { 16 16 16 }
859 8 \tuplet 3/2 { 16 16 16 } 8 8 |
863 @lilypond[verbatim,quote]
864 \new Staff { r16 c'16 ~ 8 ~ 4 ~ 2 | }
868 @code{\displayLilyMusic} and its underlying Scheme functions no
869 longer omit redundant note durations. This makes it easier to
870 reliably recognize and format standalone durations in expressions
877 Beaming exceptions can now be constructed using the
878 @code{\beamExceptions} scheme function. One can now write
880 @lilypond[verbatim,quote,relative=1]
882 \set Timing.beamExceptions =
883 \beamExceptions { 32[ 32] 32[ 32] 32[ 32] }
885 \repeat unfold 6 { c32 } |
889 with multiple exceptions separated with @code{|} bar checks
890 (writing the exception pattern without pitches is convenient but
891 not mandatory). Previously, setting the beam exceptions would
892 have required writing
895 \set Timing.beamExceptions =
897 (end . ;entry for end of beams
898 ( ;start of alist of end points
899 ((1 . 32) . (2 2 2)) ;rule for 1/32 beams -- end each 1/16
904 The most common articulations are now reflected in MIDI output.
905 Accent and marcato make notes louder; staccato, staccatissimo and
906 portato make them shorter. Breath marks shorten the previous
909 This behavior is customizable through the @code{midiLength} and
910 @code{midiExtraVelocity} properties on @code{ArticulationEvent}.
911 See @file{script-init.ly} for examples.
914 The PostScript functionality of stroke adjustment is no longer
915 applied automatically but left to the discretion of the PostScript
916 device (by default, Ghostscript uses it for resolutions up to
917 150dpi when generating raster images). When it is enabled, a more
918 complex drawing algorithm designed to benefit from stroke
919 adjustment is employed mostly for stems and bar lines.
921 Stroke adjustment can be forced by specifying the command line
922 option @samp{-dstrokeadjust} to LilyPond. When generating
923 @code{PDF} files, this will usually result in markedly better
924 looking @code{PDF} previews but significantly larger file size.
925 Print quality at high resolutions will be unaffected.
930 For older news, go to
931 @uref{http://lilypond.org/doc/v2.18/Documentation/changes/},
932 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/},
933 or @uref{../,go back} to the Documentation index.