From: <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] PIC language
Date: Thu, 20 Nov 2003 16:48:45 +0100 [thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17D124C34@XMAIL.asuch.cas.cz> (raw)
thanks a lot. i decided to generate directly ps and convert them to eps. still thinking of pic as an output format for another program i'm going to write -- not sur, however. maybe it'll be easier to do it directly in ps.
++pac.
> do we / could we have colors in PIC? What about (filled) polygons?
>
> ++pac.
One strategy I have used in the past for complicated pictures is to generate my own xfig save files. The format is not really meant to be human-readable, but it is plain text and documentation exists. xfig can read these and export them in many formats. It can even export pic format, but don't expect things like colors to work. I usually export the pictures as encapsulated postscript. You can generate the pictures however you want. I used a chain of awk scripts--inefficient, but easy to debug.
--
John Stalker
Department of Mathematics
Princeton University
(609)258-6469
---
Pøíchozí zpráva neobsahuje viry.
Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
Verze: 6.0.541 / Virová báze: 335 - datum vydání: 14. 11. 2003
---
Odchozí zpráva neobsahuje viry.
Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz).
Verze: 6.0.541 / Virová báze: 335 - datum vydání: 14. 11. 2003
next reply other threads:[~2003-11-20 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 15:48 cej [this message]
2003-11-20 16:50 ` Russ Cox
2003-11-20 18:37 ` boyd, rounin
-- strict thread matches above, loose matches on Subject: below --
2003-11-18 14:46 cej
2003-11-19 9:41 ` Douglas A. Gwyn
2003-11-19 17:05 ` boyd, rounin
2003-11-19 17:10 ` Fco.J.Ballesteros
2003-11-19 18:01 ` John Stalker
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=ACCF003CBA3D09458207DB0CB86AD17D124C34@XMAIL.asuch.cas.cz \
--to=cej@gli.cas.cz \
--cc=9fans@cse.psu.edu \
/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).