From: Duncan Hothersall <dh@capdm.com>
Subject: Re: Renaming spot colours
Date: Fri, 11 Mar 2005 14:44:32 +0000 [thread overview]
Message-ID: <4231AED0.50804@capdm.com> (raw)
In-Reply-To: <20050311142456.F072412847@ronja.ntg.nl>
Peter Rolf said
> \definecolor[PANTONE 294CV] [c=1,m=.56,y=0,k=.18]
>
> % test \framed[background=color, backgroundcolor={PANTONE
> 294CV}]{Test}
>
> \color[PANTONE 294CV] Test
>
> % the only thing that doesn't work is \PANTONE 294CV
Thanks very much for responding Peter! Interesting behaviour - the above
will process in ConTeXt, but to match the Corel name I need a space
after the '294' as well, which results in:
--
[MP to PDF] (./ifs-fmar-bk-mpgraph.1 [unknown MP special 294]
! Missing number, treated as zero.
<to be read again>
C
\@@cl@@r ->C
V
etc.
--
But in any case - did you get a functioning PDF file when you used the
above definition? Despite the fact that ConTeXt completes its run, I get
a broken file with your definition. Maybe this is because I am using
multiple tints of the spot? My color defs look like this:
\setupcolors[rgb=no,cmyk=no,spot=yes,state=start]
\definecolor[PANTONE 294CV][c=1,m=.56,y=0,k=.18]
\definecolor[IFSblue][{PANTONE 294CV}][p=1]
\definecolor[IFSbluetint][{PANTONE 294CV}][p=.2]
\definecolor[IFSblueheadertint][{PANTONE 294CV}][p=.12]
\definecolor[IFSbluetabletint][{PANTONE 294CV}][p=.15]
As I say, even with this definition (missing the final space) the PDF
result won't open in Acrobat (colour space error). Does your open?
Thanks again, much appreciated.
Duncan
dh@capdm.com
next parent reply other threads:[~2005-03-11 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050311142456.F072412847@ronja.ntg.nl>
2005-03-11 14:44 ` Duncan Hothersall [this message]
2005-03-13 19:36 ` h h extern
[not found] <20050314072143.4BCC51286D@ronja.ntg.nl>
2005-03-14 15:40 ` Duncan Hothersall
2005-03-10 9:42 Duncan Hothersall
2005-03-11 14:22 ` Peter Rolf
2005-03-11 17:23 ` Henning Hraban Ramm
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=4231AED0.50804@capdm.com \
--to=dh@capdm.com \
--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).