ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vafa Khalighi <vafa@users.berlios.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: from latex & pstricks to context
Date: Mon, 13 Jul 2009 19:21:36 +1000	[thread overview]
Message-ID: <605202f20907130221k38f26117s7215665c9c9367a7@mail.gmail.com> (raw)
In-Reply-To: <20090713110558.663d0d7e@KUBUNTU64>


[-- Attachment #1.1: Type: text/plain, Size: 636 bytes --]

>
>
> What is the sense of \startPSTRICKS ... \stopPSTRICKS ?
>

Maybe he meant:

\startpspicture

\stoppspicture

The actual macros of pstricks are defined in pstricks.tex and that is all
Plain TeX. I myself generally would do something like this in Plain TeX

\input pstricks
\pspicture(0,0)(2,2)
\psline(1,1)(2,2)
\endpspicture

\bye

and In LaTeX actually if you want to define an environment, you can use
\def\environment and \def\endenvironment. I guess then you could probably
use it in ConTeXt as

\startpspicture

\stoppspicture

and you can probable load pstricks by saying \usemodule[pstricks] or
anything that context uses.

[-- Attachment #1.2: Type: text/html, Size: 934 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2009-07-13  9:21 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
2009-07-13  9:21     ` Vafa Khalighi [this message]
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=605202f20907130221k38f26117s7215665c9c9367a7@mail.gmail.com \
    --to=vafa@users.berlios.de \
    --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).