issue 3863 - patch

2014-05-11 Thread Karol Majewski
Hi, this is my first patch ever. This should fix issue 3863. Please, test.

-Karol



0001-Issue-3863-don-t-push-away-slurs-from-dotted-notes.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


issue 3863 - patch

2014-05-11 Thread Karol Majewski
Hi, this is my first patch ever. This should fix issue 3863. Please, test.

-Karol


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond bug 2368

2012-04-24 Thread Karol Majewski
Thank you Phil.

Dear LilyPond friends: Janek, Phil, Colin,

I have another big problem now. I'm trying to find a global setting that
would allow to ignore collisions between ties and accidentals. For me, a
tie-accidental collision looks a way better than a shifted tie - especially
in tied chords in which one of the ties is unnaturaly shifted horizontaly.
I'm almost sure that it is possible to achieve this, but I don't know how.

Best wishes

PS Janek, I saw that report. I really appreciate your contribution :)




W dniu 13 kwietnia 2012 16:10 użytkownik Phil Holmes
napisał:

> **
>
>
> - Original Message -----
> *From:* Karol Majewski 
> *To:* Janek Warchoł 
> *Cc:* LilyPond Developmet Team  ; Lilypond 
> Bugs
> *Sent:* Wednesday, April 11, 2012 7:33 PM
> *Subject:* Re: lilypond bug 2368
>
> OK, thanks for explanation! Actually, I've menaged to solve my problem by
> entering hidden notes with unHidden slur in separate voice. Now the tie
> refers to the right notes and appeals to my sense of aesthetic - despite
> colliding with an accidental (take a look at the attachment).
>
> Janek, I'm not a student of Politechnika Warszawska - neither former nor
> present. I'm a former student of Akademia Muzyczna w Gdańsku :)
>
> Best Wishes
> Karol Majewski
>
> Check my suggestion at
> http://code.google.com/p/lilypond/issues/detail?id=2368 - it works better
> and is designed for this.
>
>  --
> Phil Holmes
>
>
>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond bug 2368

2012-04-13 Thread Karol Majewski
OK, thanks for explanation! Actually, I've menaged to solve my problem by
entering hidden notes with unHidden slur in separate voice. Now the tie
refers to the right notes and appeals to my sense of aesthetic - despite
colliding with an accidental (take a look at the attachment).

Janek, I'm not a student of Politechnika Warszawska - neither former nor
present. I'm a former student of Akademia Muzyczna w Gdańsku :)

Best Wishes
Karol Majewski


2012/4/11 Janek Warchoł 

> On Wed, Apr 11, 2012 at 2:36 AM, Colin Hall  wrote:
> >
> > On Sat, Apr 07, 2012 at 05:32:28PM +0200, Karol Majewski wrote:
> >>
> >> Is it possible to mark 2368 bug as critical? I think this kind of
> >> regression is a serious problem. Just take a look at my last
> >> comment:
> >>
> >> http://code.google.com/p/lilypond/issues/detail?id=2368#c6
> >
> > I agree with you that the notation output is not correct, especially
> > in the sample you provide in comment 6.
> >
> > I'm going to do my best to explain why this issue should not be marked
> > critical. I hope that others will correct my statements as necessary.
> >
> > You might not be aware that there are several open issues for Lilypond
> > that relate to the typesetting of ties and slurs. For example see
> > issue 298, referenced from issue 2368.
> >
> > http://code.google.com/p/lilypond/issues/detail?id=298
> >
> > There are others.
> >
> > As I understand it the development team have identified that a better
> > implementation of ties is possible but requires aesthetic design work
> > to establish how this feature should work before technical
> > implementation work can begin. The technical work may be substantial.
>
> Yes, i do think that it will make more sense to rewrite tie code
> bearing in mind all bad tie cases instead of fixing the issues one by
> one.  Besides, i suppose that marking this as critical will have only
> one result: next stable release will be postponed for 3 months or so.
> It won't make the bug fixed immediately, nor even soon.
>
> > Janek has a study of Lilypond's typesetting of ties and slurs which is
> > work in progress and which may provide the aesthetic design we
> > need. He mentioned it in response to your original bug report:
> >
> > http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg01203.html
>
> Yes.  The bad news is that i won't have time to finish it until
> summer.  However, if there's anyone willing to finish it, i can share
> my results and provide some guidance.  The task requires aesthetic
> sense and analytical skills, and i estimate 40 hours of work is needed
> to finish the tie analysis - no idea how long implementation will
> take.
>
> Bottom line: find someone to finish tie report and implement it's
> conclusions (or pay David to implement them - i will add EURO 50 from
> myself if this is done before May 15).
>
> i hope that didn't sound too discouraging :)
> Janek
>
> PS Karol, are you a (former) student of Warsaw University of
> Technology, Faculty of Electronics (Elka)?
>
<>___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel