From: Jim <zlists+context@jdvb.ca>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: PDF, runner, and TikZ patches
Date: Sat, 16 Mar 2024 10:21:26 -0300 [thread overview]
Message-ID: <ZfWc1hISZGwyulFp@x360.localdomain> (raw)
In-Reply-To: <57b453d4-8b13-46af-b36d-726610bc6a96@xs4all.nl>
On Fri, Mar 15, 2024 at 09:44 (+0100), Hans Hagen wrote:
> On 3/15/2024 12:53 AM, Jim wrote:
>> Max (et al),
>> were you hoping the ConTeXt distribution would ship its own
>> pgfutil-context.def, or were you hoping that someone could convince Henri
>> to put the RGB change in?
>> And, if anyone has the will to push this (or add it in to a ConTeXt
>> distribution version), I'd still like the cmyk support, even if there is no
>> ability to specify colour profiles:
>> \def\pgfutil@emu@cmyk#1#2,#3,#4,#5\@nil
>> {
>> \pgfmathsetmacro{\@red@}{(1 - #2) * (1 - #5)}%
>> \pgfmathsetmacro{\@green@}{(1 - #3) * (1 - #5)}%
>> \pgfmathsetmacro{\@blue@}{(1 - #4) * (1 - #5)}%
>> \expandafter\edef\csname\string\color@#1\endcsname
>> {\noexpand\xcolor@ {}{}{rgb}{\@red@,\@green@,\@blue@}}
>> }
>> I don't see that it would hurt anything, even if it doesn't give complete
>> cmyk support.
> We provide
> \pgf@context@registercolor
> \pgf@context@registergray
> \pgf@context@registerrgb
> \pgf@context@registercmyk
> in colo-ini that hook into the context color mechanism so be careful with
> patches. I'm not going to spend time on other solutions that can interfere
> with internals.
Thanks Hans, I was not familiar with those. The above code worked fine for
me in plain TeX (the last time I used it, anyway).
By the looks of things, Max has a vastly better idea of ConTeXt internals
than I do, and if his proposed \pgfutil@emu@rgb doesn't break anything, it
might give some confidence that the above \pgfutil@emu#cmyk won't either.
(Yeah, I know, that is hardly a robust argument of anything.)
> (I wonder when the moment comes that we have to take a snapshot of tikz and
> stay with that.)
I hope that time doesn't come, because either someone (you? :-) would be
left with an on-going job of patching the snapshot, or ConTeXt's version of
tikz would become increasingly different (and, presumably, increasingly
less capable than the "mainline" version).
Cheers.
Jim
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-03-16 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5b3c436565692c3da7b76aa4666d9d0c22eeb46b.camel@telus.net>
2024-03-14 23:18 ` [NTG-context] " Max Chernoff
2024-03-14 23:53 ` [NTG-context] " Jim
2024-03-15 0:53 ` Aditya Mahajan
2024-03-15 7:30 ` Max Chernoff
2024-03-16 13:13 ` Jim
2024-03-16 13:10 ` Jim
2024-03-16 14:20 ` Hans Hagen
2024-03-18 0:31 ` Jim
2024-03-18 8:23 ` Hans Hagen
2024-03-15 8:44 ` Hans Hagen
2024-03-16 13:21 ` Jim [this message]
2024-03-16 14:49 ` Hans Hagen
2024-03-15 8:38 ` 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=ZfWc1hISZGwyulFp@x360.localdomain \
--to=zlists+context@jdvb.ca \
--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).