At 10:19 AM 3/12/2002 +0100, Taco Hoekwater wrote:
>On Mon, 11 Mar 2002 13:33:46 -0500
>"John Culleton" <[EMAIL PROTECTED]> wrote:
>
> >
> > Context in its present form cannot handle Pstricks because
> > Pstricks generate Postscript code that is a bit scary when
> > inserted in a pdf file. (I have heard of Postscript embedded
> > in PDF but I would not want to count on it.) However
> > Metapost code is handled by an on-the-fly call to the
> > mpost program. I wonder if the same principle could be
> > used for incorporating Pstricks figures and special
> > effects into Context?
>
>Well, maybe (really, maybe) it is possible to feed some of the
>pstricks ps output to ps2edit (assuming you glue the correct
>headers in front of it). But not all of it, since sometimes
>pstricks *really* does tricks that depend on contextual information
>that is not longer present in the pdf or dvi version of a document,
>only in the dvips-generated PostScript version.
>
>And even if you are happy with the partial solution this approach
>offers, you would still need to write a driver for the ps2edit output.
>
>The easier way out (though still a lot of work) is to re-implement
>the pstricks interface using metapost and ConTeXt commands. I am
>not volunteering for that one, either. It's just too much work.
The new beta provides:
\usemodule[pstric]
\startPSTRICKS
some reasonable trickery (don't know pstricks goog enough to provide
samples)
\stopPSTRICKS
it assumes that you have gs installed and write 18 enabled
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED]
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
fall-back web server:
www.pragma-ade.nl
-------------------------------------------------------------------------
