From: "Dan Seracu" <dans@sintezis.rdsor.ro>
Cc: "NTG ConTeXt" <ntg-context@ntg.nl>
Subject: Raspuns: PSTricks vs. Metapost
Date: Mon, 7 May 2001 12:37:04 +0300 [thread overview]
Message-ID: <OEEDIGHFCEIPIMHIAKKGMEFNCBAA.dans@sintezis.rdsor.ro> (raw)
In-Reply-To: <3.0.6.32.20010507103824.019722a0@server-1>
-----Mesaj original-----
De la: owner-ntg-context@let.uu.nl
[mailto:owner-ntg-context@let.uu.nl]In numele Hans Hagen
Trimis: 7 mai 2001 11:38
Catre: Dan Seracu
Cc: NTG ConTeXt
Subiect: Re: PSTricks vs. Metapost
>i must run an very old pstricks since \pscharpath is unknown; but anyhow,
>maybe you can do this with the macros that handle outlines, see makempy.pdf
>for more info and examples
Indeed, the blur is just in 1997 version. But it works with any shape in
psTricks. (charpath was just an example).
I will have a look at makempy.pdf
Dan Seracu
prev parent reply other threads:[~2001-05-07 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 6:09 Dan Seracu
2001-05-07 8:38 ` Hans Hagen
2001-05-07 9:37 ` Dan Seracu [this message]
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=OEEDIGHFCEIPIMHIAKKGMEFNCBAA.dans@sintezis.rdsor.ro \
--to=dans@sintezis.rdsor.ro \
--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).