From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font for MetaPost graphics
Date: Fri, 4 May 2012 09:10:46 +0200 [thread overview]
Message-ID: <CALBOmsayD-W5Cer7Q0w82=wpgQej7ZuwFLVRVzHKwktqPzQATg@mail.gmail.com> (raw)
In-Reply-To: <20120503031354.4eb059a3@Zewz>
On Thu, May 3, 2012 at 3:13 AM, Marco wrote:
>
> The text in Metapost adapts to the text set in ConTeXt. But the font
> setup should *only* be set for MetaPost, not regular text.
>
> Does that mean, that MPenvironment is deprecated and does not work
> at all?
Please don't rely on my answer since I haven't been following the
development as closely as I used to in past.
But my guess is that the argument goes into the opposite way. I past
(and still in MKII) one *had to* set up fonts twice - once for the
main document and once for MetaPost since MetaPost did its own
processing of labels and MetaPost didn't see the ConTeXt font setups.
So it was "difficult" to convince MetaPost to use the same font.
Now (as Aditya explained) metapost automatically inherits font setups
from the main document and it might be that nobody ever thought of /
requested / needed to have a special setup for using different font
for MetaPost labels.
I can think of many workarounds to this, but I agree that there is a
valid reason why
\startMPenvironment
(or some other command) should be able to change the font inside
metapost labels only.
Mojca
___________________________________________________________________________________
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:[~2012-05-04 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 0:08 Marco
2012-05-03 0:22 ` Aditya Mahajan
2012-05-03 1:13 ` Marco
2012-05-04 7:10 ` Mojca Miklavec [this message]
2012-05-04 7:13 ` Aditya Mahajan
2012-05-04 11:09 ` Marco
2012-05-05 10:26 ` Hans Hagen
2012-05-05 11:24 ` Hans Hagen
2012-05-05 14:07 ` Marco
2012-05-05 16:03 ` Aditya Mahajan
2012-05-08 17:01 ` Marco
2012-05-08 17:08 ` Hans Hagen
2012-05-08 17:19 ` Marco
2012-05-08 17:34 ` Hans Hagen
2012-05-08 19:57 ` Marco
2012-05-10 8:55 ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-05-10 9:04 ` Marco
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='CALBOmsayD-W5Cer7Q0w82=wpgQej7ZuwFLVRVzHKwktqPzQATg@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).