Re: Comparison of Musescore, Sibelius and Dorico -- would like to add Lilypond

[David Bellows]

Urs,

>I think it would be good to add our stuff to the chart (not necessarily much 
>to the comments section).

If the owner of the spreadsheet allows it, then definitely. I don't
know them personally so I don't know how they feel about that. I
suppose we could create our own version if they do not agree. I'm one
of the mods in that sub so I'll be making the chart a permanent link
in the sub so either way would work (and obviously we can link to it
from anywhere else we'd like).

> not only check the given items with yes/no but also freely add to the list

I agree. The OP did ask for omissions/corrections so I would think
these (and others) would apply.

> find a way to plug the "programmability" aspect (vs. applying plugins 
> after-the-fact),    with things like complete extensibility with syntactical 
> means, conditional layout per engraving target ...    (Maybe this would even 
> warrant a new tab in the sheet)

One of Lilypond's biggest strengths! Working out meaningful/useful
parallels with the other programs would be the issue, I'm guessing?
On Tue, Nov 20, 2018 at 11:50 AM David Kastrup <address@hidden> wrote:
>
> Karlin High <address@hidden> writes:
>
> > On 11/20/2018 12:38 PM, David Bellows wrote:
> >> Over in the /r/composer sub on Reddit, a user put together a chart
> >> listing features of Musescore, Sibelius and Dorico.
> >
> > I remember seeing some past work done with comparing LilyPond to other
> > software.
> >
> > <https://github.com/engraving-challenges/main>
> > <https://lilypondblog.org/category/comparisons/>
> >
> > Other list members here may have more recent references or info.
>
> I think it's always a bit of a squeeze to compare LilyPond with other
> programs, particularly in the "challenges" department since the
> challenge is often more to the user than to the program, LilyPond being
> an open architecture with user-extensible functionality to a much larger
> degree than other programs.
>
> So a particularly user may set a checkmark "yes, can do" while this does
> not actually hold for a typical user without asking on the mailing list.
>
> --
> David Kastrup