From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: colors without \definecolor
Date: Fri, 05 Feb 2010 08:31:35 +0100 [thread overview]
Message-ID: <4B6BC957.1010205@googlemail.com> (raw)
In-Reply-To: <20100204204103.GB10019@aides.aides.com>
Am 04.02.10 21:41, schrieb Philipp Gesang:
> Hi all,
>
>
> I understand that in order to use a color with \color[somecolor]{colored
> text} I first have to \definecolor[somecolor][r=.4,g=0,b=1]. Currently
> I'm trying to do automated colorizing with the help of some lua code and
> I'd like to make up rgb vectors on the spot without having to
> \definecolor them first, e.g. something like \color[r=.4,g=0,b=1]
> {colored text}. Is there a way to achieve this in mkiv? (Right now I'm
> assigning new rgb values to the same color "name" whenever the function
> is called that concatenates the next \color[]{} statement. This seems a
> bit verbose and hacky to me.)
\colored[r=...,g=...,b=...]{...}
or
{\colored[r=...,g=...,b=...]...}
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-02-05 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 20:41 Philipp Gesang
2010-02-05 7:31 ` Wolfgang Schuster [this message]
2010-02-05 14:49 ` Philipp Gesang
2010-02-06 7:55 ` Wolfgang Schuster
2010-02-07 6:24 ` Aditya Mahajan
2010-02-07 21:56 ` Wolfgang Schuster
2010-02-08 8:19 ` Mojca Miklavec
2010-02-08 8:51 ` Wolfgang Schuster
2010-02-08 8:40 ` Hans Hagen
2010-02-08 8:55 ` Wolfgang Schuster
2010-02-08 12:28 ` 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=4B6BC957.1010205@googlemail.com \
--to=schuster.wolfgang@googlemail.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).