Hi Colin, On Thu, Mar 1, 2012 at 10:23 AM, Colin Hall <colingh...@gmail.com> wrote: > > On Wed, Feb 29, 2012 at 10:53:03PM +0100, Janek Warcho?? wrote: >> On Wed, Feb 29, 2012 at 4:38 PM, Pavel Roskin <pro...@gnu.org> wrote: >> > It's tempting to call it a regression. ??However, I don't think Lilypond >> > has logic to make ties unambiguous, so the fix would be either to >> > revert collision avoidance and decrease quality of other scores, or to >> > add such logic, which might be a difficult task. >> >> yup... since half a year i'm writing a detailed and systematic report >> on LilyPond ties, which includes cases like this. However, i'm so >> much absorbed by the other stuff (like preparing Google Summer of Code >> application for LilyPond) that i cannot finish it. > > Janek, it looks like you are familiar with this problem. > > I see a lot of open issues relating to ties. > > Rather than create a duplicate, is there an existing issue tracker that > covers this report?
I think all those issues are just scratching the surface of the tie problem. We need a thorough investigation of ties, going into the details of tie formatting and setting some general rules, thus providing general solutions to the symptoms listed currently in tracker. I'm willing to write such a report and as i said, i'm already about 40% done. But instead of finishing it, i spend my time on finding overlooked patches, preparing our application for Google Summer of Code and searching for funds, because it looks that few other people are seriously interested in doing these things. cheers, Janek _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond