>> What exactly is your argument for *not* going to version 3.x in
>> that case?
>
> [...] Since this doesn't break backward compatibility, I don't
> think we need a major version bump.
IMHO, a major version bump should also be used if something changes
fundamentally, regardless whether it is
Here is the current countdown report.
The next countdown will begin on January 9th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1799 Slur_score_state: remove programming_error - Dan Eble
On Fri, Jan 6, 2023 at 10:19 AM Jonas Hahnfeld wrote:
>
> On Wed, 2023-01-04 at 12:52 +0100, Han-Wen Nienhuys wrote:
> > Regarding versioning: the 1.x to 2.x transition was motivated by
> > radical syntax changes that necessitated converting and 'manually'
> > verifying the .ly files. Since Cairo
On Fri, Jan 6, 2023 at 4:34 PM Marnen Laibow-Koser
wrote:
[…]
> BTW, what is the current status of Mac .app builds of LilyPond? I haven’t
> seen any new builds available since the last one that I created, but maybe
> I’m looking in the wrong place.
>
I see there are builds available on the
On Fri, Jan 6, 2023 at 8:23 AM Jean Abou Samra wrote:
> Le 06/01/2023 à 10:13, Jonas Hahnfeld a écrit :
> > On Fri, 2023-01-06 at 08:48 +0100, Jean Abou Samra wrote:
> >> Jonas, is there a possibility to have access to the MacStadium
> >> node, or do you have other advice on testing this on
De : Han-Wen Nienhuys <[1]hanw...@gmail.com>
À : Jean Abou Samra <[2]j...@abou-samra.fr>
CC : Jonas Hahnfeld <[3]hah...@hahnjo.de>, lilypond-devel
<[4]lilypond-devel@gnu.org>
Date : 06/01/2023 18:53 CET
Sujet : Re: Missing items to make Cairo ready
On Sun, Jan 1,
On Sun, Jan 1, 2023 at 12:36 PM Jean Abou Samra wrote:
>
> Le 30/12/2022 à 13:08, Jean Abou Samra a écrit :
> > which means figuring out how to do PNGs via the default PS
> > backend and GS.
>
>
> I looked a bit at this.
>
> It's not insurmountable, *but*, alpha transparency is not going
> to
> Let me add a combination here: Ghostscript 10.01.0 built from
> current git (commit 462efa959) yields 28MB with extractpdfmark and
> working links (AFAICT), without changes to LilyPond. The reason is
> likely
>
On Fri, 2023-01-06 at 09:39 +, Werner LEMBERG wrote:
>
> LilyPond extract GS size
> backend pdfmark GS option of NR comments
> --
> standard no 9.56.1 -- 44MB ok
>
On Fri, 2023-01-06 at 14:41 +0100, Thomas Morley wrote:
> Am Fr., 6. Jan. 2023 um 14:26 Uhr schrieb Jonas Hahnfeld via
> Discussions on LilyPond development :
> >
> > On Fri, 2023-01-06 at 14:21 +0100, Jean Abou Samra wrote:
> > > Le 06/01/2023 à 10:19, Jonas Hahnfeld a écrit :
>
> > > I don't
Le 06/01/2023 à 14:41, Thomas Morley a écrit :
Imho, a good point to look at what users do with \postscript is the LSR.
Currently 20 snippets mention 'postscript'. I'm pretty sure most of
them can be modified to use \path etc.
Apart from https://lsr.di.unimi.it/LSR/Item?id=1060
This one is nice,
Am Fr., 6. Jan. 2023 um 14:26 Uhr schrieb Jonas Hahnfeld via
Discussions on LilyPond development :
>
> On Fri, 2023-01-06 at 14:21 +0100, Jean Abou Samra wrote:
> > Le 06/01/2023 à 10:19, Jonas Hahnfeld a écrit :
> > I don't see any markup commands other than \postscript
> > and \epsfile that we
Le 06/01/2023 à 14:26, Jonas Hahnfeld a écrit :
On Fri, 2023-01-06 at 14:21 +0100, Jean Abou Samra wrote:
Le 06/01/2023 à 10:19, Jonas Hahnfeld a écrit :
Regardless of what has been done in prior versions, it seems to me the
cleanest solution still is to remove a number of markup commands that
On Fri, 2023-01-06 at 14:21 +0100, Jean Abou Samra wrote:
> Le 06/01/2023 à 10:19, Jonas Hahnfeld a écrit :
> > Regardless of what has been done in prior versions, it seems to me the
> > cleanest solution still is to remove a number of markup commands that
> > we cannot or do not want to support
Le 06/01/2023 à 10:13, Jonas Hahnfeld a écrit :
On Fri, 2023-01-06 at 08:48 +0100, Jean Abou Samra wrote:
Jonas, is there a possibility to have access to the MacStadium
node, or do you have other advice on testing this on macOS?
I'd like to check it also works there before potentially starting
Le 06/01/2023 à 10:19, Jonas Hahnfeld a écrit :
Regardless of what has been done in prior versions, it seems to me the
cleanest solution still is to remove a number of markup commands that
we cannot or do not want to support with Cairo.
I don't see any markup commands other than \postscript
> [...] I don't see an immediate connection between the new PDF
> interpreter and file size increase (this is what "perfectly fine"
> was referring to).
Too much info is floating around, so here is a table that shows the
various possibilities we are currently investigating.
* Everything is based
On Thu, 2023-01-05 at 23:30 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> On Thu, 2023-01-05 at 13:24 +, Werner LEMBERG wrote:
> > >
> > > IMO, working with a 35mb user manual isn't materially different
> > > from working with a 10mb user manual. Both take a while to
On Wed, 2023-01-04 at 12:52 +0100, Han-Wen Nienhuys wrote:
> Regarding versioning: the 1.x to 2.x transition was motivated by
> radical syntax changes that necessitated converting and 'manually'
> verifying the .ly files. Since Cairo vs. Ghostscript doesn't affect
> the semantics of .ly files, I
On Fri, 2023-01-06 at 08:48 +0100, Jean Abou Samra wrote:
> Le 06/01/2023 à 03:19, Jean Abou Samra a écrit :
> > Le 04/01/2023 à 15:50, Jonas Hahnfeld a écrit :
> > > On the other hand, librsvg is written in Rust where I have no
> > > experience how practical it actually is to integrate into our
On Thu, 2023-01-05 at 23:55 +0100, Jean Abou Samra wrote:
> Le 05/01/2023 à 23:30, Jonas Hahnfeld a écrit :
> > What I find worrying in this discussion is that proponents of having
> > Cairo sooner than later keep dismissing the size argument, in parts
> > with very strong words, without the
21 matches
Mail list logo
