Received: by 10.66.80.166 with SMTP id s6mr1819292pax.30.1344321770273;
        Mon, 06 Aug 2012 23:42:50 -0700 (PDT)
Path: p10ni57pbh.1!nntp.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!ctu-peer!ctu-gate!news.nctu.edu.tw!usenet.stanford.edu!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From: jdaw1 <jdawise...@gmail.com>
Newsgroups: comp.lang.postscript
Subject: Re: execform, 75% faded
Date: Wed, 1 Aug 2012 01:02:13 -0700 (PDT)
Organization: http://groups.google.com
Lines: 30
Message-ID: <160df307-bbd3-461c-a94d-e03d281095d2@googlegroups.com>
References: <1390895d-c740-4357-9ad1-c5a506fce680@googlegroups.com> <B35Sr.574430$%k.181567@fx20.am4>
NNTP-Posting-Host: 207.45.249.135
Mime-Version: 1.0
X-Trace: posting.google.com 1343808214 3717 127.0.0.1 (1 Aug 2012 08:03:34 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 1 Aug 2012 08:03:34 +0000 (UTC)
In-Reply-To: <B35Sr.574430$%k.181567@fx20.am4>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=207.45.249.135;
 posting-account=Cp97SgoAAAC0t1Gya5PaPqyoafMoOtAn
User-Agent: G2/1.0
Bytes: 2718
X-Received-Bytes: 2766
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Wednesday, August 1, 2012 8:40:17 AM UTC+1, Chris wrote:
> Can't you just replace the form with a procedure containing the marking o=
perations and call the procedure instead of execform? Chris

But my output has complicated elements that are repeated many times. E.g., =
see
http://www.jdawiseman.com/2012/20120725_olympic.pdf=20
Without forms that file would be on the chunky side of ten megs.=20

I suppose the faded version of my forms could be wrapped in its own form, w=
hich would then call the =91inner=92 form as a routine rather than as a for=
m. Even though inelegant, that might be the way forward. (And anyway, Ghost=
script seems to ignore forms.) But even that has the problem that there is =
no guarantee that the innermost code parameters set colours with setgray ra=
ther than, for example, setrgbcolor.=20

=BF=94Innermost parameters=94? Huh?
This code is really code, rather than page description. See, for an idea of=
 the degree of possible parameterisation, the following:
http://www.jdawiseman.com/placemat.html
E.g., my software=92s parameters that contain arbitrary user-chosen colour-=
setting code include CrossHatchingBackgroundStrokeCode, CrossHatchingTitles=
StrokeCode, RaysStrokeCode, TastingNotesColumnStrokeCode, and others. Hence=
 re-def=92ing setgray might not suffice.

Maybe the better solution would be to grouch to Apple that Preview ignores =
PDF=92s embedded transfers.=20

Again, let me praise this bulletin board, whose regulars seem to know lots =
and know it promptly. Thank you.