From: Christian Feuersaenger <feuersaenger@ins.uni-bonn.de>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Till Tantau <tantau@tcs.uni-luebeck.de>
Subject: Re: Tikz calendar: \pgfutil undefined
Date: Mon, 23 Aug 2010 21:57:19 +0200 [thread overview]
Message-ID: <4C72D29F.3050500@ins.uni-bonn.de> (raw)
In-Reply-To: <AANLkTikvu68mw+O3vo-Cm6=eiXJLyA95+zh+-CkBtaNW@mail.gmail.com>
Hello,
thank you for the bug report. I have fixed the problem in TikZ.
Best regards
Christian
Am 19.08.2010 16:49, schrieb Mojca Miklavec:
> On Thu, Aug 19, 2010 at 14:36, David Rogers wrote:
>
>> * Fabrice Larribe<fabrice.alpha@gmail.com> [2010-08-19 06:17]:
>>
>>
>>> Hello,
>>>
>>> I have a problem to use the calendar from the Tikz/Pgf module; here
>>> is a minimal example:
>>>
>>> %---------------------------------------
>>> \usemodule[tikz]
>>> \usetikzlibrary[calendar]
>>>
>>> \starttext
>>> This should works:
>>> \blank
>>> \tikz \calendar[dates=2000-01-01 to 2000-01-31,week list];
>>> \blank
>>> but this does not !
>>> \stoptext
>>> %---------------------------------------
>>>
>>> I'm using MKII (2010-05-24) from TeX Live 2010 (Note however that I
>>> had the same problem with TeXLive 2009). The error is when the calendar
>>> library is loaded:
>>>
>>> ! Undefined control sequence.
>>> l.36 \let\tikz@atbegin@day=\pgfutil
>>> @empty
>>>
>>> I have tried the Tikz distribution from TexLive, the latest Tikz
>>> distribution from the suport Tikz page, and the distribution from the
>>> module made for ConTeXt, but the problem remains. In the past (last
>>> academic year, in may), this worked well, but I'm not able to find what
>>> has changed.
>>>
>>
>> The example still works in mkiv. (Minimal distribution, fairly recent)
>>
> The following trick solves the problem temporary, but it should be
> fixed somewhere in the source if possible. I'm not sure if it is the
> fault of ConTeXt or the fault of TikZ:
>
> \unprotect
> \usemodule[tikz]
> \usetikzlibrary[calendar]
> \protect
>
> \starttext
>
> This should works:
> \blank
> \tikz \calendar[dates=2000-01-01 to 2000-01-31,week list];
> \blank
> but this does not !
> \stoptext
> To me this looks like
>
> Mojca
>
>
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-08-23 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 10:17 Fabrice Larribe
2010-08-19 12:36 ` David Rogers
2010-08-19 14:49 ` Mojca Miklavec
2010-08-19 21:21 ` Fabrice Larribe
2010-08-20 7:47 ` Mojca Miklavec
2010-08-23 19:57 ` Christian Feuersaenger [this message]
2010-08-24 7:48 ` Mojca Miklavec
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=4C72D29F.3050500@ins.uni-bonn.de \
--to=feuersaenger@ins.uni-bonn.de \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=tantau@tcs.uni-luebeck.de \
/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).