From: Max Chernoff <mseven@telus.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: PDF, runner, and TikZ patches
Date: Fri, 15 Mar 2024 01:30:50 -0600 [thread overview]
Message-ID: <2e742e9f8e787b56f0048888b5a88c91241a1357.camel@telus.net> (raw)
In-Reply-To: <388n0p2r-9n2n-3470-r90p-12508p0spp8p@hzvpu.rqh>
Hi Aditya, Jim,
On Fri, 2024-03-15 at 01:53 +0100, Aditya Mahajan wrote:
> On Thu, 14 Mar 2024, Jim wrote:
> > 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?
>
> We can patch some of the definitions of pgfutil-context.def in m-tikz
> if really needed, but it would be preferable to first check if tikz
> maintainers are willing to merge them upstream.
Ah, okay. I was under the impression that the LMTX standalone
distribution carried a ton of TikZ patches and that ConTeXt patches
weren't really merged upstream, but it sounds like there are only a
couple small patches and upstream does merge ConTeXt patches. I'll
rebase my PR and check with upstream again. Thanks!
On Thu, 2024-03-14 at 20:53 -0300, Jim wrote:
> 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?
I've seen a few TikZ bugs/patches resolved on this list, and I know that
the LMTX standalone distribution carries patches for TikZ (although
fewer than I thought?), so this seemed like the right place to start.
> 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(a)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.
I need to rebase my current PGF PR anyways, so I'll add this in with it.
Thanks,
-- Max
___________________________________________________________________________________
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-15 7:34 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 [this message]
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
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=2e742e9f8e787b56f0048888b5a88c91241a1357.camel@telus.net \
--to=mseven@telus.net \
--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).