ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christophe Jorssen <christophe.jorssen@gmail.com>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Christian Feuersaenger <cfeuersaenger@googlemail.com>
Subject: Re: Tikz module causes errors
Date: Tue, 17 Jan 2012 17:17:19 +0100	[thread overview]
Message-ID: <CAN1usO2_9n2jUmoJYTRC=QQnBLk8eeMF1WuywrhMywG4+fkqWQ@mail.gmail.com> (raw)
In-Reply-To: <CALBOmsbhZLVX=9RRP9BVGJsUkQiDJ6bMYhjUMLRM5sCyY2AX8g@mail.gmail.com>

Hello Mojca, thanks for the follow-up.

2012/1/17 Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
> On Tue, Jan 17, 2012 at 16:00, Felix Ingram wrote:
>> I've just updated to the latest beta and the following will cause an error:
>>
>> \usemodule[tikz]
>> \starttext
>> Hello World
>> \stoptext
>>
>>
>> The error is:
>>
>> system          > tex > error on line 129 in file example.tex:
>> Undefined control sequence ...
>>
>> l.129   \catcode`\;=\active
>>
>> Obviously there is no line 129. A quick greg shows that the likely suspect is:
>> tex\texmf-modules\tex\generic\pgf\utilities\pgffor.code.tex:129
>>
>> Is this the best place to report this, or should I drop a mail to the
>> Tikz/PGF list?
>
> It's complicated because I'm not aware of any major TikZ developer
> using ConTeXt.
>
> The main question is: is this a recent problem in TikZ or in ConTeXt?
> Usually people on this list might know how to fix problems, but then
> you need to convince pgf team to accept patches. (And then Aditya
> started contributing and collecting some patches independently.)
>

If they aren't yet in the official repo, I would be happy to add those
patches. Note that I'm not a ConTeXt user, so I won't be able to test
them carefully.

> I didn't follow development of ConTeXt too closely, but I'm lead to
> believe that \active has disappeared from ConTeXt MKIV. Others will
> have to correct me if I'm wrong - I didn't check ConTeXt sources. And
> others will have to make suggestion about what to do about this.
> Patching might as easy as adding \def\active{13} somewhere on top of
> TikZ sources, but it might help to understand why Hans decided to
> remove the \active command if that is true.
>

I add it to my todo list.

> On the other hand (completely unrelated), I just realized that the
> following commit (unofficial and unreliable temporary repository):
>    https://github.com/mojca/pgf/commit/418b278dcf6a2193d0d564d9d85194bdce1e505e
> only fixes LaTeX and plain TeX and doesn't fix ConTeXt. I don't know
> what the patch is about, but I'm lead to believe that the same patch
> might be needed in ConTeXt as well if it is needed for the other two.
>

Not sure if it is needed for ContTeXt because I added the required
file on top of pgffor.code.tex that is loaded by any format one use.

I did add a \RequirePackage to the .sty file because LaTeX manages a
list of package loaded. I would be happy to do the same for ConTeXt if
it has a similar mechanism.

Best regards

-- 
Christophe
___________________________________________________________________________________
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:[~2012-01-17 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 15:00 Felix Ingram
2012-01-17 15:25 ` Hans Hagen
2012-01-17 15:28 ` Mojca Miklavec
2012-01-17 16:17   ` Christophe Jorssen [this message]
2012-01-18 11:54     ` Philipp A.
2012-01-18 12:14       ` Felix Ingram
2012-01-18 12:20         ` luigi scarso
2012-01-17 18:10   ` Hans Hagen

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='CAN1usO2_9n2jUmoJYTRC=QQnBLk8eeMF1WuywrhMywG4+fkqWQ@mail.gmail.com' \
    --to=christophe.jorssen@gmail.com \
    --cc=cfeuersaenger@googlemail.com \
    --cc=mojca.miklavec.lists@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).