From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: metafun & \sometxt: should black be "black" or "textcolor"?
Date: Sun, 6 Aug 2006 13:26:04 +0200 [thread overview]
Message-ID: <6faad9f00608060426g7d389fb4k803f2725f02ceef3@mail.gmail.com> (raw)
In-Reply-To: <44D5ADBE.3010809@elvenkind.com>
On 8/6/06, Taco Hoekwater wrote:
> Mojca Miklavec wrote:
> > Hello,
> >
> > Does anyone have any idea about what's going on here? I get blue text,
> > but a black square, although both are supposed to come out black (I
> > wouldn't mind so much, but the problem is that some text is blue and
> > some is black - I have some other testcases where this happens, but I
> > have to create a minimal example first).
>
> use \textext. \sometxt will use the text color, because it never
> reaches metapost (I assume it would be possible to intercept
> drawing options like withcolor, but that doesn't happen at the
> moment).
But the other \sometxt was indeed red - withcolor seems to work, but
only conditionally. And I have some weird examples of two texts one
after another. In some cases (if something else is drawn inbetween and
a color changed twice), then the second text will be black. But it's
quite unpredictable (that one might even be bug in my code, so I don't
want to complain before I have an example).
I while ago I also posted an interesting example with colored table
(withcolor colored only some of the cells), but that is alredy a very
complex example.
And I can't afford to use \textext. It's was too slow (approximately
factor 10) and it runs out of TeX memmory after 10 or 12 plots on
average.
Thanks,
Mojca
A question for you or Hans: can please someone explain me in a few
words what's the main strategy/philosophy behind \sometxt. I don't
understand exactly how TeX processes it (and metapost
shrinks/expands/shifts/colors) it inline.
next prev parent reply other threads:[~2006-08-06 11:26 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 [this message]
2006-08-06 14:37 ` Taco Hoekwater
2006-08-06 17:02 ` Mojca Miklavec
2006-08-06 21:48 ` Hans Hagen
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=6faad9f00608060426g7d389fb4k803f2725f02ceef3@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.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).