[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Sphinx
From: |
Werner LEMBERG |
Subject: |
Re: Sphinx |
Date: |
Tue, 25 Oct 2022 08:24:26 +0000 (UTC) |
> [...] In Sphinx, this is just a matter of reading the LilyPond input
> in a Python extension and inserting the output at that point, as is
> already done in
>
> https://pypi.org/project/sphinxcontrib-lilypond/
> or the alternative
> https://github.com/sphinx-notes/lilypond
>
> Which means that there is no longer a need to parse and pre-process
> the source ourselves with regexes in lilypond-book, with the
> associated build system fuss.
Note that it's actually a nice thing that LilyPond uses its own tool,
`lilypond-book`, for building its own documentation. This is good for
testing...
Werner
- New Lilypond logo?, Martín Rincón Botero, 2022/10/24
- Re: New Lilypond logo?, Carl Sorensen, 2022/10/24
- Re: New Lilypond logo?, Jean Abou Samra, 2022/10/24
- Is a texi2any upgrade still wanted, and what would it take? (WAS: Re: New Lilypond logo?), Karlin High, 2022/10/24
- Re: Is a texi2any upgrade still wanted, and what would it take? (WAS: Re: New Lilypond logo?), Jean Abou Samra, 2022/10/24
- Re: Is a texi2any upgrade still wanted, and what would it take?, David Kastrup, 2022/10/24
- Sphinx (was: Is a texi2any upgrade still wanted, and what would it take?), Jean Abou Samra, 2022/10/24
- Re: Sphinx, David Kastrup, 2022/10/24
- Re: Sphinx,
Werner LEMBERG <=
- Re: Sphinx, Jean Abou Samra, 2022/10/25
- Re: Is a texi2any upgrade still wanted, and what would it take?, Jonas Hahnfeld, 2022/10/25