From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Gavin via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: mp-geo Metapost package with ConTeXt
Date: Mon, 26 Jul 2021 19:01:51 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.78.908.2107261858380.2419@nqv-guvaxcnq> (raw)
In-Reply-To: <F39998F6-F9CB-42B6-854A-5CB11E7D1425@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On Mon, 26 Jul 2021, Gavin via ntg-context wrote:
> 2) While I’m having good luck with paths, colors are causing trouble. In the data set the color information is in strings with French names of the color, like “rouge.” If I hand this string to MetaPost, MetaPost doesn’t expand it into a color. It does work if it is a native color, like “red,” but not if it is a defined color and not if the color is in a Lua variable. Any suggestions?
\definecolor[rouge][red] should work. A better option will be use color palettes.
This is very old code, but will give an idea of how to use palettes:
https://github.com/adityam/visualcounter/blob/master/visualcounter.pdf Effectively all you need to do is add \setuppalet[name] at an appropriate place, and then the user can easily change the colors (rather than having them specified as part of data files).
Aditya
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-07-26 23:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 14:43 Gavin
2021-07-15 15:48 ` Hans Hagen
2021-07-15 16:22 ` Aditya Mahajan
2021-07-15 17:58 ` Hans Hagen
2021-07-15 20:30 ` Bruce Horrocks
2021-07-16 19:55 ` Hans Hagen
2021-07-17 9:53 ` Bruce Horrocks
2021-07-17 10:20 ` Henning Hraban Ramm
2021-07-17 10:45 ` Hans Hagen
2021-07-17 11:05 ` Henning Hraban Ramm
2021-10-22 9:31 ` Henning Hraban Ramm via ntg-context
2021-10-22 13:35 ` Hans Hagen via ntg-context
2021-10-22 14:16 ` Henning Hraban Ramm via ntg-context
2021-10-22 14:27 ` Hans Hagen via ntg-context
2021-07-17 10:53 ` Henning Hraban Ramm
2021-07-17 10:53 ` Hans Hagen
2021-07-17 12:42 ` Arthur Rosendahl
2021-07-17 18:50 ` Hans Hagen
2021-07-18 17:36 ` Henning Hraban Ramm
2021-07-16 16:20 ` Gavin
[not found] ` <E1B2010C-A435-46AD-BD8E-F4D930827791@me.com>
2021-07-16 19:51 ` Hans Hagen
2021-07-16 20:08 ` Alan Braslau
2021-07-26 21:29 ` Gavin via ntg-context
2021-07-26 23:01 ` Aditya Mahajan via ntg-context [this message]
2021-07-27 6:12 ` Gavin via ntg-context
2021-07-27 6:29 ` Alan Braslau via ntg-context
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=nycvar.YAK.7.78.908.2107261858380.2419@nqv-guvaxcnq \
--to=ntg-context@ntg.nl \
--cc=adityam@umich.edu \
/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).