X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fchanges.tely;h=4ea92a7cb3859e823b45f37bbc3c53d71b3a6fdb;hb=16a04d4a27ff185fd83125d965d48b534182d7d2;hp=06a1378b690e902b22337360b8385e73baf60ed1;hpb=1218da693e22c42b9f78074ad4d8f4a9151855c4;p=lilypond.git

diff --git a/Documentation/changes.tely b/Documentation/changes.tely
index 06a1378b69..4ea92a7cb3 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.18 since 2.16
+@top New features in 2.20 since 2.18
 
 @allowcodebreaks false
 
@@ -62,23 +62,25 @@ which scares away people.
 @end ignore
 
 @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
+The PostScript functionality of stroke adjustment is no longer
+applied automatically but left to the discretion of the PostScript
+device (by default, Ghostscript uses it for resolutions up to
+150dpi when generating raster images).  When it is enabled, a more
+complex drawing algorithm designed to benefit from stroke
+adjustment is employed mostly for stems and bar lines.
+
+Stroke adjustment can be forced by specifying the command line
+option @samp{-dstrokeadjust} to LilyPond.  When generating
+@code{PDF} files, this will usually result in markedly better
+looking @code{PDF} previews but significantly larger file size.
+Print quality at high resolutions will be unaffected.
 
 @end itemize
 
 @ifhtml
 For older news, go to
+@uref{http://lilypond.org/doc/v2.18/Documentation/changes/},
 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/},
-@uref{http://lilypond.org/doc/v2.14/Documentation/changes/},
 or @uref{../,go back} to the Documentation index.