Add unfold-repeats-fully function which will expand repeats in the data
Implement event-chord-reduce for reducing chords to single notes
Issue 3682/1: Implement \beamExceptions function fishing exceptions from beamed music.
Issue 3682/2: Change documentation and regtests for \beamExceptions
let RhythmicStaff use default barline extent

There is no reason to make barlines in RhythmicStaff special.
The purpose of the deleted code was probably to ensure that
the barlines were visible at all (despite the fact that there
is just one staffline in a RhythmicStaff).  However, currently
barline code takes care of this by default.

This makes barlines in DrumStaff and RhythmicStaff similar.

A comment by Keith:
The book by Kurt Stone happens to have some bar-lines in single-line percussion
staves that are as tall as a 4/4 time-signature.  Other examples in the same
book have short bar-lines like these here, and looking at some scores the short
bar-lines are more common.
Issue 3694: Use standard inclusion scheme for FreeType headers.

The most recent FreeType release (2.5.1) has changed locations for header
files.  Using the standard way, this is not visible to applications.
Support properties on articulations.

Shorthand articulations like -. can now be ArticulationEvents, not just
articulation names. Previously a shorthand created a new ArticulationEvent
with its name, so there was no way to give it properties. Now it can be (and
is, by default) an ArticulationEvent.

Note that redefining a shorthand to a string (e.g. dashDot = "staccatissimo")
still creates propertyless articulations, regardless of \staccatissimo.
Support articulations and breaths in MIDI. (issue 3664)

Articulations and breaths can alter the length and volume of the note.
(Breaths affect the previous chord.) This is controlled by their
midi-length and midi-extra-velocity properties. The standard articulations
now have these properties where appropriate.

(seconds->moment s context) is a convenience function for making
absolute durations.
web: remove old news

In particular, remove the entry about the LilyPond Report,
which is no longer reachable.
hairpin: start at left edge of a rest
small padding adjustment; issue 3630
script-column: earlier scripts support later scripts; issue 3683
Reduce offsets of \super and \sub

This brings chordNames and text superscripts into better agreement
with the shifts in user-provided scans.
Completion_*_engraver: add means to preserve scale factor; issue 3650
Make music-drawing-routines.ps require PostScript 2.0

There is no point having conditional code around setstrokeadjust and
its ilk any more.
Make stroke_and_fill? PostScript operator that fills conditionally
Don't meddle with Ghostscript's choice of currentstrokeadjust

It should be appropriate for device and resolution by default.
Issue 2658: Be serious about setstrokeadjust in PostScript primitives

This particularly concerns draw_round_box which is used for drawing
lines with a rounded ending.  If the width/height ratio or its inverse
exceeds 2, the box is considered to be a "line".  In this case, first
a clipping path is established representing the whole shape and
extended widely in the area of the "main stroke".  The reason for this
extension is to avoid both clip area and stroke competing for the
outline.  While this is not a problem for the PostScript or PDF
rendering model, the Cairo bitmap rendering library employs
Porter-Duff compositing for antialiasing amounting to "cheap man's
antialiasing" not requiring a higher rendering resolution but relying
on edges affecting a single pixel to be independent.

Porter-Duff requires us not to have multiple parallel strokes or clip
areas if we want to avoid wrong sub-pixel grayness levels (and
consequently lines appearing too thick or thin) in Cairo-based
previewers like Evince.

After establishing the clip area, a stroke is drawn through.  This
stroke may (at the PostScript device's discretion) employ
strokeadjustment further correcting the apparent thickness.
Ghostscript employs stroke adjustment when rendering at a resolution
below 150dpi.  Stroke adjustment does not pass into PDF, however, when
ps2pdf runs.

Ghostscript performs sub-pixel rendering for antialiasing which
reduces the amount of discontinuities possibly caused by joining
stroke-adjusted shapes with full shapes.

It turns out that sharper contours can be achieved by using strokepath
and fill instead of a plain stroke.  However, the resulting crisper
stems tend to combine worse with beams, so this approach has not been
pursued.
Implement option -dstrokeadjust in order to get stroked stems and strokeadjustment

This makes the stroke drawing primitives for long rounded rectangles
dependent on the setting of currentstrokeadjust.  As a result,
low-resolution bitmap devices (up to 150 dpi or so) will get stroke
adjustment applied automatically.  The option needs to get invoked
explicitly to get stroke adjustment for PDF, giving a large file size
increase and markedly better previews on a number of PDF previewers.
Add Changes entry for -dstrokeadjust and "Usage" entry.