ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jim <zlists+context@jdvb.ca>
To: Hans Hagen <j.hagen@xs4all.nl>, ntg-context@ntg.nl
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: PDF, runner, and TikZ patches
Date: Sun, 17 Mar 2024 21:31:51 -0300	[thread overview]
Message-ID: <ZfeLd71mRJlMZ4o3@x360.localdomain> (raw)
In-Reply-To: <c38a12b7-6ea8-49e1-a98d-a59f54b665e6@xs4all.nl>

On Sat, Mar 16, 2024 at 15:20 (+0100), Hans Hagen wrote:

> On 3/16/2024 2:10 PM, Jim wrote:
>> On Fri, Mar 15, 2024 at 01:53 (+0100), Aditya Mahajan wrote:

>>> On Thu, 14 Mar 2024, 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?

>>> 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.

>> Unfortunately, it seems that the maintainer feels that if we can't deal
>> with cmyk profiles, we shouldn't have cmyk at all.  I don't agree, but
>> that's where it ended.  (I was arguing for plain TeX support at the time in
>> the linked^2 message, but I was able to add the definition for cmyk to my
>> own macro file, so I was able to process examples with cmyk colours.)
> What does the maintainer mean by that ... context

The maintainer's comment was about plain TeX, not context.  Sorry if that
wasn't clear.

In any case, I should have sent my request to Max alone, rather than the
ntg-context list, because if Max was going to push something there, I was
hoping that a second appeal for cmyk colour support in plain would be
nice.  (I'm not quite ready to give up all of my plain TeX files.)

> can add profiles if configured to do so (best not to embed them) ... and
> why should there be a profile anyway ... crappy arguments ..

I agree about the colour profile, but the last time I poked that bear, my
pleas fell on deaf ears.

[And in summary, to be clear: I'm good with the colour support in ConTeXt!]

                                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
___________________________________________________________________________________

  reply	other threads:[~2024-03-18  0: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
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 [this message]
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=ZfeLd71mRJlMZ4o3@x360.localdomain \
    --to=zlists+context@jdvb.ca \
    --cc=j.hagen@xs4all.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).