From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Different colors in LaTeX and ConTeXt
Date: Wed, 13 Jul 2016 09:44:43 +0200 [thread overview]
Message-ID: <4d4ff3b4-5ffb-64da-2cd7-2fe00f9e5956@wxs.nl> (raw)
In-Reply-To: <f59e3113-6dfb-365f-0559-e004803d73df@gmail.com>
On 7/12/2016 11:17 PM, Henri Menke wrote:
> Adding \usecolors[xwi] to the example does not change anything. Looking
> at base/colo-imp-xwi.mkiv revealed, that it does not alter the way
> colors are defined, but just defines a huge bunch of additional ones.
afaiks it has the same 'gray' as tikz 'gray' and that is what you want
> I'm very sorry for the confusion. What I did was to adjust ConTeXt's
> gray to have the same grayscale value as the tikzgray. As is shown
> below, the redefinition of gray does not propagate to TikZ.
that is as Aditya mentioned probably due to the fact that some of these
built in colors are not using the normal color resolver and there's
nothing we can do about (apart from rewriting part of the tikz color
interface which is not on my agenda)
> So it seems as if gray *should* be propagated from ConTeXt to TikZ,
> which apparently takes place when loading TikZ. Moving
> \definecolor[gray][s=0.5] before \usemodule[tikz] shows this behavior.
>
> The question is how to keep colors from ConTeXt and TikZ in sync.
by defining them in your document (at least these 10 or so predefined
colors)
(you could have similar issues with colors defined in rgb or cmky in one
or the other)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2016-07-13 7:44 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
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 [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=4d4ff3b4-5ffb-64da-2cd7-2fe00f9e5956@wxs.nl \
--to=pragma@wxs.nl \
--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).