[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Slurs and ties — most difficult to make: developer has to think abou
Re: Slurs and ties — most difficult to make: developer has to think about them before his work.
Wed, 21 Dec 2016 00:53:26 +0100
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
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.
has to be sure that his future software will do with beautiful slurs
I don’t think LilyPond needs to hide from its competition, even in that
6. I think that LilyPond is not "music notation for everyone" but only
Well, if you don’t like it, nobody forces you to keep with it…