From: "George N. White III" <gnwiii@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: texexec+mpost cmr10 vs CMR10 trouble using dvips backend
Date: Mon, 16 Apr 2007 11:21:17 -0300 [thread overview]
Message-ID: <22af238a0704160721m5f77e077ua1dbfc75d0d18e9e@mail.gmail.com> (raw)
In-Reply-To: <E1HdJLt-0006PX-00@skye.ra.phy.cam.ac.uk>
On 4/16/07, Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk> wrote:
> > can also try to create the pd file by hand with "dvips -Ppdf test",
> > that gave a correct output on my system.
>
> Thanks, that works. I guess -Ppdf tells it to use map files that find
> the type1 fonts, so cmr in the metapost figures is replaced by the
> lmodern .pfb. Oh, that's not what happens: it instead finds the
> cmr10.pfb and includes it correctly. So the final document uses
> lmodern for the page number (from the ConTeXt src file) and cmr10 for
> the 'hello' from the metapost figure.
This is a hint that the underlying problem is related to map files. With the
lm-rep maps the cm "hello" should become lmodern.
> Though I'm a bit scared of -Ppdf from years ago when I think it caused
> encoding problems. A few characters didn't show up correctly in the
> pdf file, but only when using non-cmr fonts.
I think that was fixed long ago, but I rarely use .dvi anymore.
--
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia
next prev parent reply other threads:[~2007-04-16 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 4:43 Sanjoy Mahajan
2007-04-15 4:55 ` Aditya Mahajan
2007-04-15 16:45 ` Sanjoy Mahajan
2007-04-15 6:49 ` Taco Hoekwater
2007-04-15 15:23 ` Sanjoy Mahajan
2007-04-15 16:56 ` George N. White III
2007-04-17 2:03 ` Sanjoy Mahajan
2007-04-15 16:58 ` Wolfgang Schuster
2007-04-16 5:02 ` Sanjoy Mahajan
2007-04-16 14:21 ` George N. White III [this message]
2007-04-17 2:12 ` Sanjoy Mahajan
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=22af238a0704160721m5f77e077ua1dbfc75d0d18e9e@mail.gmail.com \
--to=gnwiii@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).