Bertalan Fodor writes:

> I've created the patches for the 2.4 branch. What do you say?
> Should convert-ly also be modified?

If you can, it should.  Otherwise check for #'dashed and raise an error.

> I've attached a sample image: the new output of (the new)
> input/slur-dash.ly
> True that it's too simplistic, but better than it was.

It looks fine.  I've applied it to 2.4, although it is probably more
of a new feature than a bugfix.  Maybe that was a silly thing to do.

Can yo please forward port it to 2.5 and send a new patch?  There are
more rejects than I feel like resolving right now.

Jan.


$ patch -p0 < ~/slur-pats
patching file input/test/slur-dash.ly
patching file lily/lookup.cc
Hunk #1 FAILED at 76.
1 out of 2 hunks FAILED -- saving rejects to file lily/lookup.cc.rej
patching file lily/slur.cc
Hunk #1 succeeded at 68 (offset -3 lines).
Hunk #2 FAILED at 240.
1 out of 2 hunks FAILED -- saving rejects to file lily/slur.cc.rej
patching file lily/include/lookup.hh
Hunk #1 succeeded at 22 (offset -4 lines).
patching file ly/property-init.ly
patching file scm/define-grob-properties.scm
Hunk #1 succeeded at 149 (offset -1 lines).
patching file scm/output-pdf.scm
Hunk #1 FAILED at 101.
1 out of 1 hunk FAILED -- saving rejects to file scm/output-pdf.scm.rej
patching file scm/output-pdftex.scm
Hunk #1 FAILED at 53.
1 out of 1 hunk FAILED -- saving rejects to file scm/output-pdftex.scm.rej
patching file scm/output-ps.scm
Hunk #1 FAILED at 128.
1 out of 1 hunk FAILED -- saving rejects to file scm/output-ps.scm.rej
patching file scm/output-sketch.scm
Hunk #1 FAILED at 46.
Hunk #2 FAILED at 218.
2 out of 2 hunks FAILED -- saving rejects to file scm/output-sketch.scm.rej
patching file scm/output-tex.scm
Hunk #1 FAILED at 88.
1 out of 1 hunk FAILED -- saving rejects to file scm/output-tex.scm.rej
11:06:46 [EMAIL PROTECTED]:~/lily
$ 
-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org


_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to