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

[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]

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 can add profiles if 
configured to do so (best not to embed them) ... and why should there be 
a profile anyway ... crappy arguments .. especially because when i run

\usemodule[tikz]

\startTEXpage

\definecolor [colorone] [r=0,g=0,b=0.5]
\definecolor [colortwo] [c=0,m=1]

\starttikzpicture
     \fill [colorone] (0,0) circle(2) ; % rgb
     \fill [colortwo] (0,0) circle(1) ; % cmyk
\stoptikzpicture
\setupcolors[cmyk=no]
\starttikzpicture
     \fill [colorone] (0,0) circle(2) ; % rgb
     \fill [colortwo] (0,0) circle(1) ; % rgb
\stoptikzpicture

\stopTEXpage

here i get a pdf file with rgb and cmyk. Maybe I have an old tikz and 
something changed (wouldn't be the first time). So let's forget about 
maintainers and ugly hacks, and identify what is the real problem.

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

[-- Attachment #2: oeps.pdf --]
[-- Type: application/pdf, Size: 3156 bytes --]

[-- Attachment #3: Type: text/plain, Size: 511 bytes --]

___________________________________________________________________________________
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-16 14:22 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 [this message]
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=c38a12b7-6ea8-49e1-a98d-a59f54b665e6@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=zlists+context@jdvb.ca \
    /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).