From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: pstrics module again
Date: Mon, 25 Nov 2013 13:55:07 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.03.1311251344460.780@hzvpu.rqh> (raw)
In-Reply-To: <CAPBmU9HZ_Xwe+VH_1vpXd0DqiJavPxUY6suRCgY8wSjh19RV0A@mail.gmail.com>
On Mon, 25 Nov 2013, DesdeChaves wrote:
> Dear sirs
>
> The pstrics module don't work anymore. I tried to run this simple code but
> I found a lot of errors.
>
> \usemodule[pstric]
> \starttext
> \startPSTRICKS
> \pspicture(0,0)(20,20)
> \psline(0,0)(20,20)
> \psline(1,1)(10,10)
> \endpspicture
> \stopPSTRICKS
> \stoptext
It appears that pstrick files are no longer part of the standalone
distribution, but if you copy a bunch of files, then the above example
does work.
> This module is no longer supported?
> There is still any hope of being able to use pstric and some of its
> extensions (pst-spectra, for example)?
This is what I did.
1. Compile the file. You get an error that some pstrick file is missing.
Locate that file in the texlive directory and copy it to the current
directory.
2. Repeat until you get an error that \ifx! is not a valid control
sequence.
3. Run `grep ifx! *.tex` and change all the "\ifx!#1" to "\ifx !#1".
4. Then you get an error that colo-rgb is missing. Copy colo-rgb.mkii to
the current directory as colo-rgb.tex.
5. Then you get a error message the some .pro file is missing. Find that
file from the texlive directory and copy it to the current directory.
Repeat until all errors are resolved.
Finally you'll get the correct output.
So it seems that if pstricks is added back to the minimals (so that errors
in step 1 and 5 don't happen), then it should be straightforward to get it
to work with context. (Just load the file with the correct catcode regime,
so that ! is a other character, and the error in step 2-3 will not
happen). THe error in step 3 is easy to fix by editing m-pstricks.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-11-25 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 18:05 DesdeChaves
2013-11-25 18:55 ` Aditya Mahajan [this message]
2013-11-25 19:19 ` Herbert Voss
2013-11-25 20:25 ` Aditya Mahajan
2013-11-25 20:28 ` Herbert Voss
2013-11-25 22:24 ` DesdeChaves
2013-11-25 23:08 ` DesdeChaves
2013-11-25 23:45 ` Aditya Mahajan
2013-11-25 23:53 ` Aditya Mahajan
2013-11-26 8:21 ` Herbert Voss
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=alpine.LNX.2.03.1311251344460.780@hzvpu.rqh \
--to=adityam@umich.edu \
--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).