Be serious about setstrokeadjust in PostScript primitives

Documentation/usage/running.itely

 @c -*- coding: utf-8; mode: texinfo; -*-
 
 @ignore
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  For details, see the Contributors'
     Guide, node Updating translation committishes..
 @end ignore
 
@@ skipping 646 matching lines @@
 @item @code{strict-infinity-checking}
 @tab @code{#f}
 @tab Force a crash on encountering @code{Inf} and @code{NaN} floating
 point exceptions.
 
 @item @code{strip-output-dir}
 @tab @code{#t}
 @tab Don't use directories from input files while constructing output
 file names.
 
+@item @code{strokeadjust}
+@tab @code{#f}
+@tab Force PostScript stroke adjustment.  This option is mostly
+relevant when @code{PDF} is generated from PostScript output
+(stroke adjustment is usually enabled automatically for
+low-resolution bitmap devices).  Without this option,
+@code{PDF}@tie{}previewers tend to produce widely inconsistent
+stem widths at resolutions typical for screen display.  The option
+does not noticeably affect print quality and causes large file
+size increases in @code{PDF} files.
+
 @item @code{svg-woff}
 @tab @code{#f}
 @tab Use woff font files in SVG backend.
 
 @item @code{trace-memory-frequency}
 @tab @code{#f}
 @tab Record Scheme cell usage this many times per second.  Dump the
 results to @code{FILE.stacks} and @code{FILE.graph}.
 
 @item @code{trace-scheme-coverage}
@@ skipping 410 matching lines @@
 staves are introduced in parallel, i.e. simultaneously:
 
 @lilypond[quote,verbatim]
 \score {
   <<
     \new Staff { a' a' a' a' }
     \new Staff { g' g' g' g' }
   >>
 }
 @end lilypond