From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: from latex & pstricks to context
Date: Mon, 13 Jul 2009 11:20:40 +0200 [thread overview]
Message-ID: <8D1C97D2-02F9-4648-9B76-9F054CE39B29@gmail.com> (raw)
In-Reply-To: <20090713110558.663d0d7e@KUBUNTU64>
Am 13.07.2009 um 11:05 schrieb R. Bastian:
>>> 1. is there a better way ?
>>
>> \usemodule[pstricks]
>
> "are you schuhr ? (c)"
Yes I am.
> Nebenbei : the doc http://source.contextgarden.net/m-pstric.tex
> says "%M \usemodule[pstric] etc"
'pstricks' is a synonym for 'pstric' and there are more of them for
the many presentation styles.
> i tried \usemodule[pstricks] and:
>
>>
>> \startPSTRICKS
>> ...
>> \stopPSTRICKS
> but the result is the same : dummy
I explained why this happen a while ago in a longer thread, the short
version is:
ConTeXt produce pdf files by default while pstricks requires dvi -> ps
and to do
this modifications in the pstricks module have to be done.
> What is the sense of \startPSTRICKS ... \stopPSTRICKS ?
The code between \startPSTRICKS ... \stopPSTRICKS is written to a
external file
which is then converted to pdf and afterwards included as figure (the
same
procedure as the pst-pdf or whatever is the current method use).
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-07-13 9:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 7:55 R. Bastian
2009-07-13 8:11 ` luigi scarso
2009-07-13 9:05 ` R. Bastian
2009-07-13 9:09 ` luigi scarso
2009-07-13 8:19 ` Wolfgang Schuster
2009-07-13 8:40 ` luigi scarso
2009-07-13 9:05 ` R. Bastian
2009-07-13 9:14 ` luigi scarso
2009-07-13 9:23 ` Wolfgang Schuster
2009-07-13 9:37 ` luigi scarso
2009-07-13 9:50 ` Wolfgang Schuster
2009-07-13 9:53 ` Taco Hoekwater
2009-07-13 10:02 ` luigi scarso
2009-07-13 15:12 ` R. Bastian
2009-07-13 16:03 ` luigi scarso
2009-07-13 19:22 ` R. Bastian
2009-07-13 21:01 ` Wolfgang Schuster
2009-07-13 9:20 ` Wolfgang Schuster [this message]
2009-07-13 9:21 ` Vafa Khalighi
2009-07-13 8:46 ` Mojca Miklavec
2009-07-13 9:23 ` R. Bastian
2009-07-13 9:47 ` Mojca Miklavec
2009-07-13 9:53 ` Mojca Miklavec
2009-07-13 10:29 ` Renaud Aubin
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=8D1C97D2-02F9-4648-9B76-9F054CE39B29@gmail.com \
--to=schuster.wolfgang@googlemail.com \
--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).