ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: batela <batela@tugamail.com>
Subject: Re: PsTRICKS in Context
Date: Mon, 19 Jun 2006 17:29:34 +0100	[thread overview]
Message-ID: <02af09524e0d061d7df7faf416662678@tugamail.com> (raw)
In-Reply-To: <4496C833.508@wxs.nl>


Thanks.

But, in this LATEX_to_Context migration, I need to convert at hand 
several latex commands. For example:

\begin{itemize} to \startitemize

\end{itemize} to \stopitemize


\begin{table}_to_\starttable

and so on.

this is a very hard task.

Perhaps I need to make: perl -ps 's/\begin{itemize}/\startitemize/g'  
*.tex





Em 19/06/2006, às 4:52, Hans Hagen escreveu:

> batela wrote:
>> To all,
>>
>> I am the author of a physics booklet written in LATEX+PsTRICKS.
>> Now,  my I intend  is to make one improved version in Context, but I
>> have many
>> schems with  PSTRICKS commands. Did you know  a easy way  to make the
>> migration?
>>
> there is a module, m-pstric.tex
>
>
> \usemodule[pstrick]
>
> \startPSTRICKS
>   \pspicture(0,0)(10,10)
>     \dorecurse{10}{\psline(0,0)(\recurselevel,10)}
>     \dorecurse{10}{\psline(0,0)(10,\recurselevel)}
>   \endpspicture
> \stopPSTRICKS
>
> an option is to put the graphics in separate files and/or use checksum 
> trickery as used in m-r (not yet done)
>
> Hans
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
>                                              | www.pragma-pod.nl
> -----------------------------------------------------------------
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
Um Abraço,

Jorge Magalhães

  reply	other threads:[~2006-06-19 16:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2014-12-14 17:45 PSTricks " 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
2014-12-15 21:27             ` Alan BRASLAU
2014-12-16  9:32           ` luigi scarso
2014-12-15  9:28 Akira Kakuto
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

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=02af09524e0d061d7df7faf416662678@tugamail.com \
    --to=batela@tugamail.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).