Jean Abou Samra <j...@abou-samra.fr> writes: > Personally, my dream would be to switch to a different documentation > tool entirely, like Sphinx, which supports HTML, LaTeX and Texinfo > output, with extensive HTML customization possibilities, and would > not need so much build system fuss (lilypond-book etc.),
How do you imagine the LilyPond images to arrive in the documentation without the "build system fuss"? The bulk of the lilypond-book fuss is about efficiently compiling ten thousands of small LilyPond fragments without recompiling duplicates appearing in multiple translations. > and supports internationalization via po files on top of that. But > that is going to be controversial and the amount of work is magnitudes > larger :) The problem is that an advertised feature set is comparatively useless for imagining the amount of work before arriving at a satisfactorily smoothly operating and efficient solution. It is not uncommon to have a proof of concept running within less than a week, with a satisfactory efficient solution adding years of development. -- David Kastrup