From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: texexec+mpost cmr10 vs CMR10 trouble using dvips backend
Date: Sun, 15 Apr 2007 18:58:30 +0200 [thread overview]
Message-ID: <20070415185830.50bb1c72.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <E1Hd6Zj-0000Ui-00@skye.ra.phy.cam.ac.uk>
On Sun, 15 Apr 2007 16:23:35 +0100
Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk> wrote:
> > If you set prologues := 1 in the mp file, that should help.
>
> That still gave Courier fonts after including fig.1 in test.ps.
>
> > In a new metapost (texlive2007) you can even generate an
> > image with the font included by using prologues := 3.
>
> That worked. [I'm using MetaPost 0.993 (Web2C 7.5.6) from the Debian
> texlive2007-2 packages.]
>
> >From p.24 of the corresponding mpman.pdf manual:
>
> It is worth noting that the default value prologues:=0 is
> sufficient for graphics included in TEX-based documents.
>
> Does that need a slight exception added to it? Or have I
> misconfigured something in the toolchain from .tex + .mp to .ps? By
> the way, the figure works fine with prologues := 0 if I include it
> (using epsf.tex) in a plain-TeX document.
>
> So I think there's something slightly off about what ConTeXt is doing.
>
> -Sanjoy
>
Hi Sanjoy,
can also try to create the pd file by hand with "dvips -Ppdf test",
that gave a correct output on my system.
The texexec way used Courier in the PS-File, the dvips use cmr10 in the
PS-File.
Wolfgang
next prev parent reply other threads:[~2007-04-15 16:58 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 [this message]
2007-04-16 5:02 ` Sanjoy Mahajan
2007-04-16 14:21 ` George N. White III
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=20070415185830.50bb1c72.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@googlemail.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).