From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: texexec --mptex text?
Date: Wed, 21 Dec 2005 18:34:41 +0100 [thread overview]
Message-ID: <43A99231.9060805@elvenkind.com> (raw)
In-Reply-To: <0CF281B0-71CA-4250-A5A2-062A070FD769@science.uva.nl>
Hi,
Hans van der Meer wrote:
> Why are the o's colliding?
They shouldn't, but ...
> font shown to be Courier Truetype (Macintosh OSX).
> And why is the fount Courier instead of the expected ComputerModern
> SansSerif?
I assume your previewer doesn't know how to display ec-lmss12, so it
uses the font it has rigged as a last resort: Courier.
Try running mptopdf on test-1.1 before starting the previewer.
> File tmpgraph.log shows context loading ec fonts (why not lm now)?
> yours sincerely,
As Hans said, the "ec-" part is the 'ec' (aka 'cork' aka 'T1') encoding.
Cheers, Taco
next prev parent reply other threads:[~2005-12-21 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 15:58 Hans van der Meer
2005-12-21 16:31 ` Hans Hagen
2005-12-21 17:34 ` Taco Hoekwater [this message]
2005-12-21 18:12 ` Hans van der Meer
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=43A99231.9060805@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).