Re: lilypond-book

[David Kastrup]

Martin Tarenskeen <address@hidden> writes:

> I am looking into the possibilities of lilypond-book and LaTeX.
> I tried using LaTeX years ago but was frightened by the strange
> non-wysiwyg approach and mysterious commands then.
>
> But since I have begun to use and like LilyPond, which uses a similar
> approach, I decided to give LaTeX a second chance. And indeed, looking
> into some LaTeX tutorials again all seems much less strange to me now.
>
> Lilypond-book allows me to combine the power of LilyPond and LaTeX.
>
> It would be even more convenient if a lilypond package for LaTeX would
> exist that would allow me to enter LilyPond code directly in a LaTeX
> document, without needing lilypond-book as an extra step.
>
> something like this in a LaTeX document:
>
> \usepackage[options...]{lilypond}
> \begin{lilypond}
> ...some lilypond code ...
> \end{lilypond}
>
> For now the lilypond-book solution works fine, and I can imagine
> Lilypond developers don't feel much urge to write a LaTeX package for
> something that is already perfectly possible using lilypond-book?

It is one of the motivations that I changed the optional argument syntax
for lilypond environments to agree with that of LaTeX.

About €800 of effort, it would require write18 functionality to be
enabled and/or still use a variant of lilypond-book behind the scenes,
and \end{lilypond} has to remain visible to LaTeX.  If you wanted to
have LaTeX actually write out the LilyPond code itself (rather than
asking LilyPond-book), you could not usually use it anywhere where
verbatim environments don't work (like footnotes or inside of other
arguments).  So using lilypond-book for that makes best sense.

-- 
David Kastrup