From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Different colors in LaTeX and ConTeXt
Date: Tue, 12 Jul 2016 11:07:28 -0400 (EDT) [thread overview]
Message-ID: <alpine.OSX.2.02.1607121102060.5341@nqv-znpobbx> (raw)
In-Reply-To: <959a3c5c-c11a-d8f9-f031-05f6b128313e@wxs.nl>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1181 bytes --]
On Tue, 12 Jul 2016, Hans Hagen wrote:
> On 7/12/2016 3:44 PM, Henri Menke wrote:
>> Dear Hans,
>>
>> thanks for your reply. Indeed there are color definitions in
>> `pgfutil-context.def`. However, they are commented out with the message
>>
>>> % no need for x colors (users can load it if needed)
>>> ...
>>> %\pgfutil@definecolor{gray}{gray}{0.5}
>>
>> If I add
>>
>>> \csname pgfutil@definecolor\endcsname{gray}{gray}{0.5}
>>
>> to my document the gray shows up fine. So that's for sure a feasible
>> workaround.
>>
>> Can you comment on the phrase »no need for x colors (users can load it
>> if needed)«? I'm not quite sure what it means and it suggests that
>> there exists a proper solution to my color problem.
>
> normally you want the same colors in tikz images as in context so then
> defining them in tikz is creating incompatibilities (your case is the
> reverse and a-typical)
However, without such redefinitions, tikz does not understand ConTeXt
colors. I use a similar workaround in my documents as well.
Perhaps, one could define a macro `\enabletikzcolors[...list..]` that will
do the appropriate translations.
Aditya
[-- 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-07-12 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 11:53 Henri Menke
2016-07-12 12:29 ` Hans Hagen
2016-07-12 13:44 ` Henri Menke
2016-07-12 14:44 ` Hans Hagen
2016-07-12 15:07 ` Aditya Mahajan [this message]
2016-07-12 16:03 ` Hans Hagen
2016-07-12 18:23 ` Aditya Mahajan
2016-07-12 19:39 ` Henri Menke
2016-07-12 20:01 ` Alan BRASLAU
2016-07-12 20:03 ` Hans Hagen
2016-07-12 21:17 ` Henri Menke
2016-07-13 7:44 ` 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.OSX.2.02.1607121102060.5341@nqv-znpobbx \
--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).