From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Reconfigure mpgraph
Date: Sun, 12 Feb 2006 12:11:45 +0100 [thread overview]
Message-ID: <43EF17F1.3030409@elvenkind.com> (raw)
In-Reply-To: <loom.20060211T153519-7@post.gmane.org>
Sebastian Sturm wrote:
> Hi,
>
> I'd like to use the Metapost graph module together with the Euler math fonts.
> Unfortunately, mpgraph seems to expect its label font to have the decimal
> dot at position 46/2E, whereas according to \showfont the eurm10 dot is
> at position 58/3A. This results in Metapost omitting all dots from the tick
> mark labels. Is there an easy way to reconfigure mpgraph (I looked at the
> source code, but that seems very confusing to me) to look for
> its dots at the other position?
Can't you use an Euler text font? These have the dot in the right place.
Cheers, Taco
next prev parent reply other threads:[~2006-02-12 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 14:44 Sebastian Sturm
2006-02-12 11:11 ` Taco Hoekwater [this message]
2006-02-12 14:31 ` Sebastian Sturm
2006-02-12 17:58 ` Taco Hoekwater
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=43EF17F1.3030409@elvenkind.com \
--to=taco@elvenkind.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).