From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: noheaderandfooterlines messes with colors
Date: Mon, 3 Aug 2015 10:36:33 -0400 (EDT) [thread overview]
Message-ID: <alpine.OSX.2.02.1508031032580.53315@nqv-znpobbx> (raw)
In-Reply-To: <55BF3618.8070108@wxs.nl>
On Mon, 3 Aug 2015, Hans Hagen wrote:
> \hbox\bgroup\forcecolorhack\starttikzpicture
> \draw(0,2) node[color=red]{This should be red};
> \draw(0,0) node[color=red]{This is red};
> \stoptikzpicture\egroup
Tikz colors are broken when using anything other than red, blue, or green.
I know that colors defined in ConTeXt used to work in Tikz, so perhaps
something has changed recently at the TikZ end.
@Mojca: The following definitions can go in t-tikz.tex
\usemodule[tikz]
\define\starttikzpicture
{\hbox\bgroup\forcecolorhack\tikzpicture}
\define\stoptikzpicture
{\endtikzpicture\egroup}
\starttext
\red{This is red} \qquad \darkred{This is dark red}
\starttikzpicture
\draw (0,2) node[color=red] {This is red};
\draw (4,2) node[color=darkred] {This is dark red};
\stoptikzpicture
\stoptext
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2015-08-03 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 18:46 Eric Détrez
2015-08-01 20:32 ` Aditya Mahajan
2015-08-03 8:38 ` Eric Détrez
2015-08-03 9:36 ` Hans Hagen
2015-08-03 14:36 ` Aditya Mahajan [this message]
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.OSX.2.02.1508031032580.53315@nqv-znpobbx \
--to=adityam@umich.edu \
--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).