Here is the current countdown report.
The next countdown will begin on 2024-04-03
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!2289 convertrules.ly: Fix some regular expressions - Werner Lemberg
https://g
Hi Aaron,
That is a great suggestion. Thanks a lot!
I have been playing around with it and noticed that in order to keep the
order of the generated braille identical to the Lilypond code, I would
need to also override the top-level-score-handler, and possibly others
to keep track of the order
On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote:
> Step 4: Remove compatibility code for Guile 2.2
> This can happen after we made one or two releases with only Guile 3.0.
This is now up for review in the following merge request:
https://gitlab.com/lilypond/lilypond/-/merge_requests/2293
On 2024-04-01 3:47 am, Maurits Lamers via Discussions on LilyPond
development wrote:
Hey all,
I also asked this question on the lilypond-user mailing list, but I
gather it is a rather complex question for that list. As you might be
aware, I have been working on a braille extension for Lilypond
Hey all,
I also asked this question on the lilypond-user mailing list, but I
gather it is a rather complex question for that list. As you might be
aware, I have been working on a braille extension for Lilypond which
(based on the music info extraction example) renders Lilypond scores
into mus
