Re: [Groff] lilypond and groff

[Grégoire Babey]

Dear Werner, 

GREAT! Everything is working now and I can complete the memo I was
writing.  Thank you for answering me so soon!
I know you prefer Latex to write this kind of papers. So you have been
propably even searching an trying for a while. More thanks :o)



And yes, it would be big help to add this infos on the glilypond man
page. 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. 

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.) 



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?

 
Regards
Grégoire










Le dimanche 01 février 2015 à 08:35 +0100, Werner LEMBERG a écrit :
> [please include the groff mailing list]
> 
> > qwer
> > .lilypond start
> > \version "2.18.2"
> > \header {
> >     footer = ""
> >     tagline = ""
> >   }
> >
> >   \paper {
> >     indent = 0
> >   }
> >
> > {
> >   c' e' g' e'
> > }
> > .lilypond end
> >
> > The input-file is named qwer1.me
> 
> Ah, looking up an old thread in the groff mailing list, I see that you
> have to suppress headers and footers too to get a tight bounding box.
> 
>   qwer
>   .lilypond start
>     \version "2.18.2"
>     \header {
>       footer = ""
>       tagline = ""
>     }
> 
>     \paper {
>       indent = 0
>       oddHeaderMarkup = #f
>       evenHeaderMarkup = #f
>       oddFooterMarkup = #f
>       evenFooterMarkup = #f
>     }
> 
>     {
>       c' e' g' e'
>     }
>   .lilypond end
> 
> The first step is to call glilypond.
> 
>   glilypond qwer1.me > qwer-groff.me
> 
> > I groff it through
> > groff -me -kpo qwer1.me > qwer1.ps
> 
> The `o' in `-kpo' is invalid if not supplied with a list of output
> pages, thus you get the `bad output page list' error.  You should
> rather try
> 
>   groff -me -kp qwer-groff.me > qwer-groff.ps
> 
> since option `-o' is useless for a single output page.  Of course,
> for this small test document you neither need `-p' nor `-k' also.
> 
> I can now view the resulting PS file with the `gs'.  Note that for
> security reasons most programs calling ghostscript as a subprocess use
> its `-dSAFER' option.  This is the reason that you can't view
> `qwerty.ps' with e.g. `gv' or `evince' because the lilypond snippets
> use ghostscript's `.loadfont' operator, which is not allowed in safer
> mode.
> 
> To get a (normal) PDF file, call ps2pdf.
> 
>   ps2pdf -dNOSAFER qwer-groff.ps 
> 
> Option `-dNOSAFER' cancels the effect of `-dSAFER'.
> 
> All these details should be added to the glilypond man page.
> Unfortunately, Bernd doesn't respond the last few weeks...
> 
> 
>     Werner