Re: Prefer luatex for documentation

> Am I understanding it correctly that with this plus the already > merged https://gitlab.com/lilypond/lilypond/-/merge_requests/1715, > we don't need the Autoconf UTF-8 locale searching stuff anymore, at > least for now? Correct. I've already cleaned up all index entries in previous commits so

PATCHES - Countdown to November 30

Here is the current countdown report. The next countdown will begoin on November 30th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: No patches in Push at this time. Countdown: !1747 documentation-g

Automated testing for users' LilyPond collections with new development versions

This message intrigued me: In it, Eric Benson reported a setup that allows testing new versions of LilyPond on a sizable body of work in a somewhat automated fashion. Now, could automation like that also make use of the

Re: Prefer luatex for documentation

Le 28/11/2022 à 22:23, Jean Abou Samra a écrit : Le 28/11/2022 à 11:55, Werner LEMBERG a écrit : It is the doc autogeneration infrastructure that is not correctly writing the NR appendix files as UTF-8. It should be using set-port-encoding!. Will you submit a MR? https://gitlab.com/lilypond/

Re: Prefer luatex for documentation

Le 28/11/2022 à 11:55, Werner LEMBERG a écrit : It is the doc autogeneration infrastructure that is not correctly writing the NR appendix files as UTF-8. It should be using set-port-encoding!. Will you submit a MR? https://gitlab.com/lilypond/lilypond/-/merge_requests/1747 OpenPGP_signature

Re: Prefer luatex for documentation

> It is the doc autogeneration infrastructure that is not correctly > writing the NR appendix files as UTF-8. It should be using > set-port-encoding!. Will you submit a MR? Werner

Re: Prefer luatex for documentation

Date: Mon, 28 Nov 2022 09:18:25 +0100 >> `texindex` is just one part of the problem.[*] We also need a UTF-8 >> locale for both `makeinfo` and `lilypond-book` – without it, the >> output for both PDF and HTML is simply wrong. My standard example >> is the incorrect display of the degree sign in t

Re: Prefer luatex for documentation

> Le 28 nov. 2022 à 09:18, Jean Abou Samra a écrit : > > I would like to understand why this happens. The French translation has > accents everywhere, and I never saw problems while reading it. Judging from > the image, the texi input itself output by lilypond-book is buggy (since > LilyPon

Re: Prefer luatex for documentation

> Le 28 nov. 2022 à 06:54, Werner LEMBERG a écrit : > >  >>> What I'm now working on are macros for `configure.ac` to find a >>> UTF-8 locale, which is important for the documentation generation >>> in the long run. [...] >> >> Phooey, that sounds complicated. I wonder if it would not take