Doc-it: update
Doc-es: typo.
Issue 3572: convert-ly should produce several backup files for each invokation

This supports and documents the -b option for numbered backups.  This
was actually written primarily by Eluze.
Making flat flags available

Issue 3591

The markup-command 'note-ny-number' and the relvant regression-
tests are extended, too.
The sippet 'using-alternative-flag-styles.ly' from
Documentation/snippets/new/ isn't changed for now, will be tackled
in a follow up.
Issue 3602/1: Remove Dynamic_engraver.
Run scripts/auxiliar/update-with-convert-ly.sh
Issue 3602/2: Rename lily/new-dynamic-engraver.cc to lily/dynamic-engraver.cc
Issue 3602/3: Rename New_dynamic_engraver to Dynamic_engraver in lily/dynamic-engraver.cc
Doc-it: chapter 1 completed
Merge branch 'issue3602' into staging

Done as a merge commit since otherwise the conversion rules and their
application would have required splitting into two parts in order to
keep all commits in master compilable: too much mess for too little
benefit.
Merge branch 'translation' into staging

Conflicts:
	Documentation/it/usage/updating.itely
Issue 3313: Add the command \offset

The ability to offset values of various properties would be a useful
enhancement of LilyPond.  Currently, this is possible for default values
of the property 'control-points using the \shape command.  The following
patch seeks to generalize the application of offsets to grob properties.
Both overrides and tweaks are supported, on the model of \shape and
\alterBroken.

Offsets are currently limited to three data types: number, number-pair,
and number-pair-list (this last is defined by this patch and represents
the type used, for example, by 'control-points).  Offsets are limited to
the properties listed in the grob descriptions contained in
`scm/define-grobs.scm'.  Offsets will be reckoned against an override
currently in effect; otherwise, the default setting from the grob
description will be used.
scripts: improve strip-whitespace.py

previous version barfed when it was called on a directory
(which could happen for example when called with a wildcard).
Also, add comment.
Typo fix: \CadenzaOn/Off -> \cadenzaOn/Off
Doc: Change Balloon Text example

Issue 3608

Remove redundant \balloonLengthOff command

Change paragraph to say 'does not' rather, than currently stated, as 'does'
NR: Correct explanation of ledger line override

Issue 3556

Correct the explanation of how the ledger-line-thickness
override is calculated.
Issue 3611: Parser: remove non-closed expressions from function_arglist_nonbackup_common
Revert "Issue 3205: opening bar check causes crash if \score contains the \midi block"

This reverts commit c83a3afbc51c62769cbb8963371d37b312bbcd42.

The replacement of Simple_music_iterator with Music_iterator in
lily/bar-check-iterator.cc made bar checks at the start of music
expressions inoperative altogether, even when not at a bar boundary:

{ a a { | } a a }

stopped producing a diagnostic.  Issue 3205 instead needs to be fixed
together with issue 2392 which apparently may be called "Segfault in
Midi when Simple_music_iterator is used at the beginning of an
implicitly created context".
Issue 3603: Make \tweak ... Grob equivalent to \override rather than \once \override

This simplifies several uses of tweak for both tweak and override.
When desired, one can use \once \tweak in order to get either tweak or
override-once semantics: in the case of the tweak semantics, \once
will just ignore the contained expression.
Issue 3581: New data types for adjusting MIDI control functions

Signed-off-by: David Kastrup <dak@gnu.org>