Re: Make \footnote a post-event (issue 6203044)

[dak]

Reviewers: Keith, Graham Percival,

Message:
As you can see, this draft comment did not get out in time but was
forgotten.

Looks like changing the version to 2.15.34 is now in your ballpark.


http://codereview.appspot.com/6203044/diff/1018/input/regression/collision-seconds.ly
File input/regression/collision-seconds.ly (right):

http://codereview.appspot.com/6203044/diff/1018/input/regression/collision-seconds.ly#newcode1
input/regression/collision-seconds.ly:1: \version "2.14.0"
On 2012/05/10 06:53:33, Keith wrote:
> convert-ly changed this because I mis-typed an older version number
when
> expanding this test.  I'll change it later to "2.15.34" unless you do
it with
> this commit.

Sounds rather like something you should directly push to staging.  I'll
catch up with it when rebasing.

Description:
Make \footnote a post-event

Also run scripts/auxiliar/update-with-convert-ly.sh

The result should work, but for sanity's sake, this should be followed
by a manual conversion of all occurences of

<>\footnote ...
note-or-chord

into

note-or-chord\footnote ...

It would have been too error-prone to try detecting a suitable
note-or-chord sequence to move across automatically.

Please review this at http://codereview.appspot.com/6203044/

Affected files:
  M Documentation/de/notation/input.itely
  M Documentation/es/notation/input.itely
  M Documentation/fr/notation/input.itely
  M Documentation/ja/notation/input.itely
  M Documentation/notation/input.itely
  M input/regression/collision-seconds.ly
  M input/regression/footnote-auto-numbering-page-reset.ly
  M input/regression/footnote-auto-numbering-vertical-order.ly
  M input/regression/footnote-auto-numbering.ly
  M input/regression/footnote-break-visibility.ly
  M input/regression/footnote-footer-padding.ly
  M input/regression/footnote-spanner.ly
  M input/regression/footnote.ly
  M input/regression/in-note.ly
  M ly/music-functions-init.ly
  M python/convertrules.py
  M scm/define-music-types.scm