ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: PSTricks
Date: Mon, 09 Apr 2001 14:46:47 +0200	[thread overview]
Message-ID: <3.0.6.32.20010409144647.0236b300@server-1> (raw)
In-Reply-To: <20010409131624.A12183@gauss.noos.fr>

At 01:16 PM 4/9/01 +0200, Damien WYART wrote:
>* Hans Hagen <pragma@wxs.nl> [010409 12:31]:
> 
>> [pstricks will never work with pdftex, but mp can]
>
>What about pdftricks, then ? [ Not tested by myself ]

hm, sounds new, will need to take a look at it

The main complication with pstricks is that it uses ps for calculations;
passing each one to e.g. mp or a calculation script is not efficient, and
using tex for that purpose needs a rewrite of pstricks; and in some
occasions awareness of the history / page is needed as well as font
handling. So, one solution is to make those pictures into independent ones,
use for instance gs to convert them, and merge them into the page stream
[as can be done with eps]. Real complicated interaction with the page could
be a problem, but as with all things, there is possibly a solution. This is
not so much different from using mp runtime. 

My main problem with pstricks is its inaccuracy [althoyghj i admit that i
only looked into it on behalf of ppchtex which used pictex first, pstricks
as second option, and in context metapost by default].

if there is a real need for it i can look into pdftricks and see if it can
be supported [i wonder what nice dirty trick is actually used -)] 

Hans    
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      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
-------------------------------------------------------------------------


  parent reply	other threads:[~2001-04-09 12:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-06 21:56 PSTricks Giuseppe Bilotta
2001-04-08  2:40 ` PSTricks Ed L Cashin
2001-04-09  5:34 ` PSTricks Dan Seracu
2001-04-09 10:31   ` PSTricks Hans Hagen
     [not found]   ` <20010409131624.A12183@gauss.noos.fr>
2001-04-09 12:46     ` Hans Hagen [this message]
2001-04-10 10:26   ` Re[2]: PSTricks Giuseppe Bilotta
  -- strict thread matches above, loose matches on Subject: below --
2009-04-24  6:16 PSTricks David Arnold
2009-04-24  6:24 ` PSTricks Wolfgang Schuster
2009-04-24  7:39 ` PSTricks luigi scarso
2009-04-24  7:57   ` PSTricks Wolfgang Schuster
2006-12-29  4:41 PSTricks Mojca Miklavec
2006-12-29  6:11 ` PSTricks Aditya Mahajan
2006-12-30  0:23   ` PSTricks Sanjoy Mahajan
2006-04-01 18:42 PSTricks David Arnold
2006-04-01 19:19 ` PSTricks Renaud AUBIN
2006-04-02  6:07 ` PSTricks Aditya Mahajan
2000-09-04 13:22 PSTricks Dan Seracu
2000-09-04 14:04 ` PSTricks berend
2000-09-04 14:18 ` PSTricks Hans Hagen
2000-09-05  6:41   ` PSTricks Dan Seracu
2000-09-05  6:42     ` PSTricks Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3.0.6.32.20010409144647.0236b300@server-1 \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).