ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: PSTricks in Context
Date: Mon, 15 Dec 2014 17:26:24 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.03.1412151723220.26610@hzvpu.rqh> (raw)
In-Reply-To: <CALBOmsbw=Yg=h0iSJj5U5WeB5EcOmXgDydPdSQPdTYTqaYsW1g@mail.gmail.com>

On Mon, 15 Dec 2014, Mojca Miklavec wrote:

> On Mon, Dec 15, 2014 at 9:45 PM, Herbert Voss wrote:
>> Am 15.12.2014 um 15:27 schrieb Mojca Miklavec:
>>
>>> First of all I had to use Kakuto-san's example, adding something like
>>>
>>> \pspicture(0mm,0mm)(30mm,30mm)
>>> ...
>>> \endpspicture
>>>
>>> in front and at the back (which is extremely ugly to see in ConTeXt).
>>
>> I see,
>>
>> \tikzpicture
>> ..
>> \endtikzpicture
>>
>> looks nicer ;-)
>
> Well, that also, but in that case it would be \starttikzpicture ...
> \stoptikzpicture. The pairs \tikzpicture ... \endtikzpicture and
> \pspicture ... \endpspicture are plain TeX commands.
>
> I would expect from ConTeXt to support
>
> \startpspicture
> ...
> \stoppspicture
>
> out of the box (if it supported PST properly).

This is a minor issue that can be easily fixed by a few lines of wrapper 
code in m-pstricks.

pstricks relies on other parts of the tex ecosystem (a tex.pro file IIRC, 
and some binaries) that are not shipped with ConTeXt standalone. It will 
be great if MKIV supports pstricks out of the box. There are some very 
nice pstricks packages that are hard (and time consuming) to replicate.

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
___________________________________________________________________________________

  reply	other threads:[~2014-12-15 22:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14 17:45 context context
2014-12-15  8:13 ` Mojca Miklavec
2014-12-15  8:28   ` Herbert Voss
2014-12-15  8:55     ` Mojca Miklavec
2014-12-15 11:53       ` Herbert Voss
2014-12-15 13:06         ` luigi scarso
2014-12-15 20:46           ` Herbert Voss
2014-12-16 12:27             ` luigi scarso
2014-12-31 14:58               ` luigi scarso
2014-12-15 14:27         ` Mojca Miklavec
2014-12-15 20:45           ` Herbert Voss
2014-12-15 21:18             ` Mojca Miklavec
2014-12-15 22:26               ` Aditya Mahajan [this message]
2014-12-15 21:27             ` Alan BRASLAU
2014-12-16  9:32           ` luigi scarso
  -- strict thread matches above, loose matches on Subject: below --
2014-12-16 10:04 Akira Kakuto
2014-12-16 10:35 ` luigi scarso
2014-12-16 13:07   ` Herbert Voss
2014-12-17 21:22     ` Context NTG
2014-12-18 14:29       ` Mojca Miklavec
2014-12-18 18:53         ` Context NTG
2014-12-15  9:28 Akira Kakuto
2006-06-19  2:45 Metapost: point along path and metaobj Aditya Mahajan
2006-06-19 14:03 ` Taco Hoekwater
2006-06-19 15:46   ` PsTRICKS in Context batela
2006-06-19 15:52     ` Hans Hagen
2006-06-19 16:29       ` batela

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.1412151723220.26610@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).