ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: DesdeChaves <desdechaves@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: pstrics module again
Date: Mon, 25 Nov 2013 22:24:27 +0000	[thread overview]
Message-ID: <CAPBmU9EctcjnEhms8Ok3O_OD9fBAXJK4haaWT4P5KERxqp2ckQ@mail.gmail.com> (raw)
In-Reply-To: <5293B2F9.1010007@FU-Berlin.DE>


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

 radical solution

 Download and unpack the PSTRicks-TDS.tar to a directory
 cp ./PSTricks-TDS/tex/generic/*/*.tex .
 perl -pi.back -e 's/\ifx!#1/\ifx !#1/g;' *.tex
 rm -rf *.back
 cp /usr/local/texlive/2013/texmf-dist/tex/context/base/colo-rgb.mkii
./colo-rgb.tex
 run context

 change in m-pstric.* files ps2pdf to pstopdf

tanks a lot

Jorge


2013/11/25 Herbert Voss <Herbert.Voss@fu-berlin.de>

> Am 25.11.2013 21:25, schrieb Aditya Mahajan:
>
>
>  \unprotect
>> \input pstricks
>> \protect
>>
>> and therefore when ConTeXt sees \ifx!#1 it thinks that \ifx! is a
>> csname. Adding a space after \ifx avoids that.
>>
>> As I said in my previous message, this is easy to fix at ConTeXt end
>> defining an appropriate catcode regime before inputing pstricks.
>>
>> So, the pstricks package does not need to be changed, but the ConTeXt
>> code that is calling the package needs to be adapted.
>>
>
> ok, understood.
>
> thanks,
> Herbert
>
> ____________________________________________________________
> _______________________
> 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
> ____________________________________________________________
> _______________________
>



-- 
Atentamente

DesdeChaves

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

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2013-11-25 22:24 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
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 [this message]
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=CAPBmU9EctcjnEhms8Ok3O_OD9fBAXJK4haaWT4P5KERxqp2ckQ@mail.gmail.com \
    --to=desdechaves@gmail.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).