On Tue, Jun 23, 2020 at 9:32 PM Jean Abou Samra <j...@abou-samra.fr> wrote:
> Hi Paolo, > > Le 23/06/2020 à 21:09, Carl Sorensen a écrit : > > Paolo, > > > > On Tue, Jun 23, 2020 at 12:33 PM Paolo Prete <paolopr...@gmail.com> > wrote: > >> 2) Considering that a Pedal cautionary is *essential* in *every* serious > >> score, I really encourage the developers to fix this in the development > >> branch. I forward this post to the devel ml. > > There is no way to "encourage the developers to fix this". The > > developers are all volunteers, and work on what they find interesting. > > > > If you really want this worked on, here are a few ideas: > > > > 1) Ask if there are any developers who are willing to do it as work > > for hire. And then either pay the developer or try to get together a > > group of users to collectively pay the developer. > > > > 2) Learn about LilyPond development and provide your own patch. This > > is one of the benefits of open source projects. You can "scratch your > > own itch". > > > > 3) Try to find somebody else who might make the change, either out of > > interest or for money. For example, you might find a computer science > > student at a local school who is interested in music. > I think filling an issue on https://gitlab.com/lilypond/lilypond/ > (with Type::Enhancement) would be a good starting point.This will > sort-of officialize that this feature is desired and create a place > to discuss it. Then, if that issue is really important to you, > This issue is not *important for me*. It is an *essential* feature for any score. If it won't be implemented, then I'll find a way to fix it on myself (and then share the result, as I always did). Best, P >