PATCHES - Countdown to January 4

Here is the first countdown report for the year. The next countdown will begin on January 4th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1786 Revise some script priorities - Martín Rincón Botero https:

Re: Ghostscript disabled features and EPS

Le 02/01/2023 à 11:49, Jonas Hahnfeld a écrit : On Mon, 2023-01-02 at 00:56 +0100, Jean Abou Samra wrote: I just realized one thing about the Ghostscript trimming that was extensively discussed on -user some time ago (https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00045.html): Th

Re: The hel-arabic.ly file story...

Amir Czwink writes: > Thanks for your responses. > > First and foremost: I'm not trying to accuse or hold someone > accountable. I'm trying to understand (and idealistically improve) the > process. [...] > But I wonder, how the process will work then? Every one simply commits > what he thinks i

Re: The hel-arabic.ly file story...

On 1/2/2023 10:25 AM, Amir Czwink wrote: But I wonder, how the process will work then? Every one simply commits what he thinks is best and we regularly overwrite each others contributions? LilyPond's process for contributions is documented here, in the Contributor's Guide:

Re: The hel-arabic.ly file story...

Le 02/01/2023 à 17:25, Amir Czwink a écrit : But come on, you don't need to be experts to discover code duplication. Even if you're not familiar with Arabic music, the same blocks of code in a single file from a single contribution can possibly be spotted and it should be in your best interest to

Re: The hel-arabic.ly file story...

> But come on, you don't need to be experts to discover code > duplication. [...] Right now, you are only ranting. This doesn't help anybody. Please provide a patch or series of patches (ideally, as an Merge Request) that we can discuss further. Everyhing else is pointless, as far as I can s

Re: The hel-arabic.ly file story...

Thanks for your responses. First and foremost: I'm not trying to accuse or hold someone accountable. I'm trying to understand (and idealistically improve) the process. Okay, maybe my expectations were a bit too high considering the need of comparing a contribution against the documentation in a m

Re: Unbreakable space in texinfo and html

Am Mo., 2. Jan. 2023 um 13:30 Uhr schrieb Werner LEMBERG : > > > > Here the next one: What's html for @@code@{TupletBracket@} > > ? > > Are you talking about > `it/texidocs/controlling-tuplet-bracket-visibility.texidoc`? There, > `@@code@{TupletBracket@}` is wrong; it should be > `@code{TupletBrac

Re: Unbreakable space in texinfo and html

Am Mo., 2. Jan. 2023 um 13:23 Uhr schrieb Werner LEMBERG : > > > > > I could do (in the description) > > > > (1) fa > > (2) ‘fa’ > > (3) 'fa' > > > > What do you recommend? > > Assuming that people are going to translate this I would do (1). > > > Werner Thanks, done. Harm

Re: Contributor guide not mentioned for 2.24

Le 02/01/2023 à 12:01, Jonas Hahnfeld via Discussions on LilyPond development a écrit : I think it is, nobody is supposed to contribute directly to a "stable" version; that is what we have "development" versions for. IMO this makes perfect sense. Ok, you convinced me. OpenPGP_signature Desc

Re: LSR update?

Am Mo., 2. Jan. 2023 um 13:33 Uhr schrieb Werner LEMBERG : > > > >> Ideally, there would be a git repository to which we can actually > >> push the new files (to retain the editing history), and a script > >> that regenerates the database automatically – and vice versa. > > > > Werner, actually it'

Re: LSR update?

>> Ideally, there would be a git repository to which we can actually >> push the new files (to retain the editing history), and a script >> that regenerates the database automatically – and vice versa. > > Werner, actually it's less work than expected. > Currently /Documentations/snippets/new con

Re: Unbreakable space in texinfo and html

> Here the next one: What's html for @@code@{TupletBracket@} > ? Are you talking about `it/texidocs/controlling-tuplet-bracket-visibility.texidoc`? There, `@@code@{TupletBracket@}` is wrong; it should be `@code{TupletBracket}` instead. The HTML equivalent to `@code{TupletBracket}` is `TupletBr

Re: Unbreakable space in texinfo and html

> I could do (in the description) > > (1) fa > (2) ‘fa’ > (3) 'fa' > > What do you recommend? Assuming that people are going to translate this I would do (1). Werner

Re: LSR update?

Am Mi., 28. Dez. 2022 um 07:17 Uhr schrieb Werner LEMBERG : > > > > Lateron, when LSR runs 2.24.0, we need to insert all snippets from > > /Documentation/snippets/new. This is tedious, any help would be > > great. > > Sebastiano, if we send you an archive with all updated snippets: Do > you have a

Re: Unbreakable space in texinfo and html

Am So., 1. Jan. 2023 um 22:24 Uhr schrieb Aaron Hill : > > On 2023-01-01 11:21 am, Thomas Morley wrote: > > May I ask further: > > What are the html equivalents of @qq{…} and @q{…}? > > If you are looking for HTML entities, there are several online resources > (such as [1]) that list them. > > [1]:

Re: Unbreakable space in texinfo and html

Am So., 1. Jan. 2023 um 23:58 Uhr schrieb Werner LEMBERG : > > > > What are the html equivalents of @qq{…} and @q{…}? > > There is no stand-alone equivalent to `@q`. If you write > > ``` > foo > ``` > > it gets converted by `pandoc` to > > ``` > ``foo'' > ``` > > which `makelsr.pl` in turn convert

Re: Contributor guide not mentioned for 2.24

On Sat, 2022-12-31 at 19:59 +, Werner LEMBERG wrote: > While > >   https://lilypond.org/development.html > > mentions the CG, it is missing from > >   https://lilypond.org/manuals.html > > Is this intentional? I think it is, nobody is supposed to contribute directly to a "stable" version;

Re: Ghostscript disabled features and EPS

On Mon, 2023-01-02 at 00:56 +0100, Jean Abou Samra wrote: > I just realized one thing about the Ghostscript trimming that > was extensively discussed on -user some time ago > (https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00045.html): > > The regtest markup-eps.ly does not compile on