From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Latest betas break tikz matrix
Date: Sun, 11 Sep 2011 23:39:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1109112324130.6981@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <alpine.LNX.2.02.1109112246510.6981@ybpnyubfg.ybpnyqbznva>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1682 bytes --]
On Sun, 11 Sep 2011, Aditya Mahajan wrote:
> On Sun, 11 Sep 2011, Philipp A. wrote:
>
>> 2011/2/23 Mathieu Boespflug <0xbadcode@gmail.com>
>>
>>> Hi all,
>>>
>>> just as a followup and for the mailing list archives, the solution is
>>> to use both Aditya's suggestion to turn on \donknuthmode, as well
>>> replacing the & signs with their interpretations, namely
>>> \pgfmatrixnextcell. Thank you Aditya for the suggestion.
>>>
>>> Regards,
>>>
>>> Mathieu
>>
>>
>> umm, i can’t seem to get it to work. i use the mkiv minimals…
>>
>> no combination of \donknuthmode, \nonknuthmode, \pgfmatrixnextcell and
>> “replace ampersand=foo”, that i tried, seems to work.
>>
>> can anyone give me a minimal example of a working tikz matrix in a context
>> document? (preferrably something that prevents me from littering everything
>> with “\pgfmatrixnextcell”)
>
> One way around this is to re-read part of tikz module code under the right
> catcode regime (ideally this should be done by t-tikz). I still cannot get &
> to work, but using \& is a reasonable shortcut.
>
> Here is a working example:
>
> \usemodule[t-tikz]
> \usetikzlibrary{matrix}
>
> \unprotect
> \ReadFile{pgfmodulematrix.code.tex}
> \protect
A slightly more robust solution is to load the attached module instead of
t-tikz. (It also patches \usetikzlibrary). However, I cannot figure out
what is the expected catcode of & inside a tikz \matrix. So, you will
still need to use amserand replacement=\&.
Note that this sets the catcode of ! to other (as expected by tikz). In
the past, circuittikz has some troubles with the catcode of !.
Aditya
[-- Attachment #2: Type: APPLICATION/x-tex, Size: 1469 bytes --]
[-- Attachment #3: 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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-09-12 3:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 1:39 Mathieu Boespflug
2011-02-23 2:10 ` Aditya Mahajan
[not found] ` <AANLkTim5kURLU-pKFBtzGsnP9C0bJy4W9T50JZTKrXL0@mail.gmail.com>
2011-02-23 16:38 ` Mathieu Boespflug
2011-02-23 22:39 ` Mathieu Boespflug
2011-09-11 14:38 ` Philipp A.
2011-09-12 2:58 ` Aditya Mahajan
2011-09-12 3:39 ` Aditya Mahajan [this message]
2011-09-12 9:16 ` Philipp A.
2011-02-25 21:05 ` 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=alpine.LNX.2.02.1109112324130.6981@ybpnyubfg.ybpnyqbznva \
--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).