If you're into guitar stuff, there's something else you might be
interested in cleaning up and getting working ...
I wrote a capo feature, but it sort of fell by the wayside. If you're
using chord notation, it puts "Capo G" or whatever at the start of the
piece, and transposes the chord and puts it in brackets after the main
chord.
I think I can find it and pass it over to you - I'm sure I've got the
patch files, and the feature branch is, I think, still there but
moribund - if you search for "guitar capo" on the list, you might find
it. As I remember it really just needs cleaning up - unfortunately my
scheme-fu wasn't up to it.
Cheers,
Wol
On 12/03/2021 02:56, David Stocker wrote:
I will look into this and read back up on the contributing docs. It's
been a while, but since I do software every day now, I hope learning
will be quicker! (probably not 😉)
On 3/11/2021 5:50 PM, Federico Bruni wrote:
This is a great news!
Yes, the development is still active. I guess you'd better subscribe
to lilypond-devel for questions about development.
Can I suggest something to work on? :-)
You may remember that Marc Hohl bend.ly file had bending notation for
both Staff and TabStaff.
Harm's implementation is more powerful.. see this commit:
https://gitlab.com/lilypond/lilypond/-/commit/376a8c362fea5b754ff383dd62f2664f8dea13bb
but it lacks the bending notation on Staff.
