> Luatex is always available with modern tex distros (say at least 5
> yrs probably more). In fact pdftex _is_ luatex...
??? Definitely not.
```
> pdftex --version
pdfTeX 3.141592653-2.6-1.40.24 (TeX Live 2022)
kpathsea version 6.3.4
Copyright 2022 Han The Thanh (pdfTeX) et al.
There is NO
>> In https://gitlab.com/lilypond/lilypond/-/merge_requests/1714 I
>> suggest that we prefer luatex for building the documentation. What
>> do people think?
>
> What I'm missing here is the bigger picture: Are we going to
> continue adding support and switching between TeX engines one after
>
Luatex is always available with modern tex distros (say at least 5 yrs
probably more). In fact pdftex _is_ luatex...
I feel texlive is a stable enough bet for people...
L
On Sat, 19 Nov 2022, 22:15 Jonas Hahnfeld via Discussions on LilyPond
development, wrote:
> On Sat, 2022-11-19 at 10:19
Le 19/11/2022 à 22:29, Jonas Hahnfeld a écrit :
I suppose this is referring to
https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00272.html
? It's always helpful to link to explicit messages, lilypond-user sees
far too much traffic for me to keep fully up with it and topics are
On Fri, 2022-11-18 at 11:06 +0100, Jean Abou Samra wrote:
> Hi,
>
> As illustrated by a recent message on lilypond-user, the
> GC issue on Windows is still there for very large scores
> in 2.23.81.
I suppose this is referring to
On Sat, 2022-11-19 at 10:19 +, Werner LEMBERG wrote:
> In https://gitlab.com/lilypond/lilypond/-/merge_requests/1714 I
> suggest that we prefer luatex for building the documentation. What
> do people think?
What I'm missing here is the bigger picture: Are we going to continue
adding support
Thank you for your quick answer. Running make again was indeed all it took
for it to start working again.
Am Sa., 19. Nov. 2022 um 18:37 Uhr schrieb Jean Abou Samra <
j...@abou-samra.fr>:
> Le 19/11/2022 à 18:31, Martín Rincón Botero a écrit :
> > Hello,
> >
> > I'm trying to make a new
Le 19/11/2022 à 18:31, Martín Rincón Botero a écrit :
Hello,
I'm trying to make a new test-baseline for the automated regression tests.
This time I'm not able to do it. I made first make clean and then make
test-baseline checking out the current git master all while being inside of
the build
Hello,
I'm trying to make a new test-baseline for the automated regression tests.
This time I'm not able to do it. I made first make clean and then make
test-baseline checking out the current git master all while being inside of
the build directory. After a while I get:
testing
On Nov 19, 2022, at 05:19, Werner LEMBERG wrote:
>
> Attached you can find an example that demonstrates (a), taken from the
> MR.
The sample LGTM. Beyond that, I prefer not to involve myself in the discussion.
—
Dan
In https://gitlab.com/lilypond/lilypond/-/merge_requests/1714 I
suggest that we prefer luatex for building the documentation. What do
people think?
The main advantage of using luatex is complete microtype support; this
was activated recently in `texinfo.tex`, and XeTeX doesn't support it
in its
>> Looking into
>>
>> https://gitlab.com/lilypond/lilypond/-/pipelines
>>
>> I see that for every merge I do, two pipelines are executed.
>> Apparently, this doesn't happen for Jean. What am I doing wrong?
>
> Nothing. There is one pipeline on the merge request to test it,
> then one
>> It would be necessary to add another property to stencils, say, an
>> 'active' flag, so that they can be intentionally taken out of a
>> skyline.
>
> YAGNI. Just use ly:stencil-outline.
OK.
> Are you mindful that ly:make-stencil is a low-level function? If you
> use it, you need to have an
13 matches
Mail list logo
