PATCHES - Countdown to October 4
Here is the current countdown report. The next countdown will begin on October 4th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !2119 NR: Document cluster styles - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2119 !2118 NR: Document that default header layout expects single-line entries - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2118 !2117 NR: Improve 'Known issue and warnings' for section 'Automatic accidentals' - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2117 !2116 point-and-click: Enable backslash in paths on non-Windows platforms - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2116 Countdown: !2125 Remove stuff related to the `festival` program and `lilysong` script - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2125 !2124 paper.scm: Remove `ledger-line-thickness` paper variable - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2124 !2122 In-notes - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2122 !2121 Fix crash for trailing moveto in stencil-integrate - David Kastrup https://gitlab.com/lilypond/lilypond/-/merge_requests/2121 !2120 Don't set explicit (zero) Y extent for `LyricExtender` and `LyricHyphen` - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2120 Review: !2126 Remove texi2html substitution from build-doc-tree.sh - Jonas Hahnfeld https://gitlab.com/lilypond/lilypond/-/merge_requests/2126 !2123 NR: Improve and fix description if `clip-regions` variable - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2123 New: No patches in New at this time. Waiting: No patches in Waiting at this time. Cheers, Colin
Re: [RFC] HTML documentation with texi2any
On Sun, 2023-09-03 at 14:40 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > For a possible timeline, we could wait for the release of LilyPond > 2.25.8 (probably September 16/17 because I'm travelling next weekend, > unless Jean wants to do it again) and then merge the changes right > after. This happened on Sunday 17. > This would still allow us to maybe shake out some first problems > and also clean up some workarounds remaining from texi2html. The first two big follow-up merge requests went in the week after. Given no major complaints from developers so far, I will likely go ahead and release a new unstable version next weekend (October 7/8) so that users also get to see it and report problems, if there are any. Plus many other fixes are lining up as well Jonas signature.asc Description: This is a digitally signed message part
Re: unnecessary line in `define-context-properties.scm`?
Werner LEMBERG writes: > I wonder whether line 35 in file `define-context-properties.scm` is > necessary. AFAICS, the `map` call in functions > `all-user-translation-properties` and > `all-internal-translation-properties`, together with the following > > ``` > (define-public all-translation-properties > (append all-user-translation-properties > all-internal-translation-properties)) > ``` > > completely construct `all-translation-properties`. Why the additional > `set!`? Looks like an oversight in commit 7b22e2505be517e58c3f922ddc53f1b7b0bd -- David Kastrup
unnecessary line in `define-context-properties.scm`?
I wonder whether line 35 in file `define-context-properties.scm` is necessary. AFAICS, the `map` call in functions `all-user-translation-properties` and `all-internal-translation-properties`, together with the following ``` (define-public all-translation-properties (append all-user-translation-properties all-internal-translation-properties)) ``` completely construct `all-translation-properties`. Why the additional `set!`? Werner
