From: Hans Hagen <pragma@wxs.nl>
Subject: Re: metafun & \sometxt: should black be "black" or "textcolor"?
Date: Sun, 06 Aug 2006 23:48:14 +0200 [thread overview]
Message-ID: <44D6639E.9030800@wxs.nl> (raw)
In-Reply-To: <44D5FEBB.8020808@elvenkind.com>
Taco Hoekwater wrote:
> Quick fix: You can start your MP code with an explicit color
> initialization.
>
> \startMPcode
> special "0 setgray";
> ......
> \stopMPcode
>
>
> A hack, I know. MetaPost should be able to distinguish between
> draw p
> and
> draw p withcolor (0,0,0)
> but currently it can't (because the structure is initialized
> as (0,0,0)). It is not quite a bug either, because there may
> well be MP code out there that depends on this.
> In fact, probably code by Knuth, Hobby, Jacko, and Hans ;-)
>
-)
i think that (given that in principle mp produces stand alone ps code)
it should start out with black; when embedding as eps or when used as
xform in pdf thsi probably is automatically taken care of
it makes sense to let mp do that for you; there are a few places where
context forces the defaultcolor; we can make it an opion in the mp topdf
converter as well
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-08-06 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 2:32 Mojca Miklavec
2006-08-06 8:52 ` Taco Hoekwater
2006-08-06 11:26 ` Mojca Miklavec
2006-08-06 14:37 ` Taco Hoekwater
2006-08-06 17:02 ` Mojca Miklavec
2006-08-06 21:48 ` Hans Hagen [this message]
2006-08-06 22:02 ` Hans Hagen
2006-08-07 8:04 ` Mojca Miklavec
2006-08-07 8:15 ` Taco Hoekwater
2006-08-07 9:40 ` Mojca Miklavec
2006-08-07 10:25 ` 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=44D6639E.9030800@wxs.nl \
--to=pragma@wxs.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).