Re: [Groff] lilypond and groff

[Werner LEMBERG]

> The 2 steps I miss there are:
> 
> 1) you can not inster .lilypond start ....  .lilypond end in the
>    input code, and just send it through groff. You have to use
>    glilypond first.

But this *is* documented!  Perhaps you can provide a patch that
improves the wording in glilypond.man.

> 2) you cannot open the .ps file, you have to go on to .pdf, and
>    there you can read it. (If somebody knows just nothing about
>    ghostscript - as I do - he will propably give up when the .ps
>    won't load.)

Yes, both a missing feature and lack of documentation.  The latter is
certainly easier to fix.

> Now just an idea. AFAICS glilypond is a kind of pre-processor like
> .tbl.  Was it possible to resume the 2 steps you show me with an
> option?  Why not an option -y [to groff]?

I think Bernd will eventually implement that.  However, this isn't
available yet.


    Werner