Re: [Groff] groff_lilypond v0.2

[Bernd Warken]

> Von: "Deri James" <address@hidden>
>
> It may be a mis-type (ps <-> pdf). .PSPIC is definitely not supported by
> gropdf, but is by grops.

You are right, `groff -Tpdf' does not work.  But I used `groffer' which still
generates a ps-file and converts it by `gs' or `ps2pdf' into `pdf'.  And that
works.  So there has to be done something in `-Tpdf'.  But `groff -Tps' does not
work for me as well there are only device images shown, not the eps-images.

> The reason is because although eps files can be
> embedded in a pdf but they are not displayed by any pdf viewers and are only
> used when the pdf is printed. The only image type supported by gropdf is
> another pdf file. There are many tools which will convert different formats to
> a pdf. I do want to develop a similar .PDFPIC macro but the problem is to
> reliably extract the size of the graphic in the pdf to be embedded. Unlike eps
> files which have a handy bounding box for the graphic which can be queried
> from within a groff file with the .psbb request, the actual size of a pdf
> image is harder to ascertain.
>
> It is not even sufficient to rely on ghostscript's bbox device, since this
> does not give the media size but rather the size of the stroked image, so does
> not include any transparent border around the outside of the stroked image.
> The actual size of the pdf image is in fact a product of MediaBox ArtBox
> TrimBox BleedBox CropBox settings within the pdf, which happen to be "current"
> at the point the image is stroked.
>
> Without knowing the actual size of the image it is not possible to write a
> high level equivalent of .PSPIC, and you must use the lower level \X’pdf:
> pdfpic file alignment width height line-length’.
>
> Deri