problematic output v2.1.33.hwn1

[David Bobroff]

When I saw Han-Wen's post on info-lilypond about "serious problems with
randomly misplaced symbols" being fixed I was optimistic.  I compiled
and tried it out.  While some of the issues were fixed (no more
"phantom" beams floating around, for example...) I'm now getting some
really bizarre spacing problems.  I've got bar lines slicing through
whole measure rests. (!!!)

Also, if I recall correctly, there was a short thread recently about key
changes and bar lines.  I remember that this same topic came up some
months back because I brought it up.  I had to use break-align-order (or
somesuch) to change it to suit me.  Then, soon thereafter, the default
behavior of Lily was altered to do exactly what I wanted.  Now it seems
to have been changed again.

Two or three revisions ago, at a linebreak/key change Lily did:

bar line / cancelled key / new key / new line

Now, as of 2.1.33.hwn1:

cancelled key / new key / barline / new line

This short example illustrates it:


\score { 
    \notes  {
        \clef F
        \time 4/4
        \key f \major
        f1 \bar "||" \break
        \key  g \major
        g1
    }
    \paper {linewidth = 6 \cm}
}

I performed a reality check to be sure I was not talking nonsense.  I
looked at linebreak/keychanges in rehearsal this morning and it was as I
thought it should be.  That is: barline / cancelled key (optional) / new
key / line break

This was in a couple of Breitkopf & H\"artel printings as well as a
Boosey and Hawkes printing.  After rehearsal I looked through my library
and found that no matter what kind of printing, the practice was:

barline / cancelled key / new key / line break

Whether it was real engraved (with stamps, hammers, and gougers) music,
photoreproduced manuscript or even <gasp>
Finale/Sibelius/Score/What-have-you.  **Occasionally** the order was:

cancelled key / barline / new key

..but this was the exception rather than the rule.

I don't mean to lecture anybody on the topic.  I'm just saying that
until very recently LilyPond was doing this chore just fine and now I
think it has gone wrong.

I'm also wondering if this has anything to do with the weird spacing.

-David