[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-bug
Subject:    =?UTF-8?Q?Re:_Slurs_and_ties_=e2=80=94_most_difficult_to_make:_deve?= =?UTF-8?Q?loper_has_to_think_a
From:       Simon Albrecht <simon.albrecht () mail ! de>
Date:       2016-12-20 23:53:26
Message-ID: ca6f633b-8255-5e65-019b-31d8f0b689fc () mail ! de
[Download RAW message or body]

Hi Miroslaw,

again: this is not a very good bug report as described on our website: 
<lilypond.org/bug-reports.html>. Please be specific, report one 
well-defined problem and not a major rant of seven items. As Thomas 
already said – code examples are quasi-mandatory, except for very 
special cases.

On 21.12.2016 00:24, Mirosław Doroszewski wrote:
> 4. Why the image from main web site of LilyPond has correct shaping
> ties after breaking in two systems and my work accordingly to manuals
> creats ugly shaping of slurs and ties?

LilyPond's automatic formatting is very good, but it doesn't work 
equally well in every possible case. For that, tweaks are available, 
like \shape. (You'll find that in the manuals.)

> 5. When developer thinks to make project of music notation software,
> he has to decide, what interface will be using by future software.

I can assure you that a lot of thought has gone into the development of 
LilyPond… and some really good thought, as well, I daresay.

>   He
> has to be sure that his future software will do with beautiful slurs
> and ties.

I don't think LilyPond needs to hide from its competition, even in that 
respect.

> 6. I think that LilyPond is not "music notation for everyone" but only
> for specialists.

Well, if you don't like it, nobody forces you to keep with it…

Best, Simon

_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

[prev in list] [next in list] [prev in thread] [next in thread]