Revert "Adds ly:generic-bound-extent function."

This reverts commit 0b032b61be1224b2cce061df60aa89ea5aa89c07.
Revert "format-metronome-mark and metronome-markup don't support styles other than default"

This reverts commit 12e6948fe2fa0c73103748fd815a7c93fdc3677e.
Merge remote-tracking branch 'origin/translation' into stable/2.18
Run scripts/auxiliar/makelsr.py
Merge remote-tracking branch 'origin/translation' into stable/2.18
Merge remote-tracking branch 'origin/translation' into stable/2.18
Revert "Issue 1334: A \score-lines markup list command for multi-lines embedded scores"

This reverts commit c2f316e714d49e8d9557a7148f92b53ff96db21b.

Conflicts:
	scm/define-markup-commands.scm
Issue 3651: Simplify incipit.ly snippet

After issue 3187, considerably less trickery is needed for getting the
incipits to align with the main score.
Run scripts/auxiliar/makelsr.py
Merge remote-tracking branch 'origin/translation' into stable/2.18
Issue 3656: Problems building Lilypond 2.17.95 with libc++ for use with llvm

std-vector.hh did not include config.hh but relied on it
Issue 3656/2: disambiguate our own ::to_string from std::to_string

Conflicts:
	lily/volta-repeat-iterator.cc
Fold function_arglist_backup_common into function_arglist_backup

After the last refactoring, function_arglist_backup does not need a closed
variant, so there is no point in an extra non-terminal.
parser: move FRACTION into embedded_scm_bare_arg

It's a closed expression; not having to parse it with separate rules
reduces the amount of cruft in the rules.
Make make_music_from_simple return music rather than a list in \chordmode
Let a PITCH_IDENTIFIER optionally be followed by octave modifiers

This makes pitch identifiers more similar to note names.  There is no
point in keeping the distinction just for triggering syntax errors
on music that has no sensible other interpretation.
Make sure optional arguments accepted as pitches stay pitches when reparsing
Let simple_music possibly return a pitch in \chordmode
Issue 3663: Crash with \repeat ... \alternative and \remove "Bar_engraver"

This approach is just poking around in the dark and removing Scheme
error messages.  In particular substituting the original glyph for
left-bar-line and right-bar-line (when missing) in calls to
span-bar::compound-bar-line seems fishy, and the original logic
for setting left-bar-broken if left-bar-line is not even present
is also not clear to me.

The results for the example in the bug report:
form = \new Staff \with {
  \remove "Bar_engraver"
} \repeat volta 2 {
    s1
} \alternative {
    s1 % first ending
    s1 % second ending
} % form

\score {
  <<
    \form
  >>
} % score
are also not identical with the 2.16 results: the volta brackets now
run into each other; before there was a gap.

It fixes the crash.  I have no idea what a proper fix would look like.
Merge remote-tracking branch 'origin/translation' into stable/2.18