Bug#295205: metapost figures in xdvi with tex text

[Chris Walker <chrisw@chiark.greenend.org.uk>]

On Tue, Feb 15, 2005 at 01:45:24PM -0800, Paul Vojta wrote:
> On Tue, Feb 15, 2005 at 01:00:03PM +0100, Frank K?ster wrote:
> > Stefan Ulrich <stefanulrich@users.sourceforge.net> wrote:
> > 
> > > There doesn't seem to be an easy way for Xdvi to detect that it's not
> > > a standalone PS file. (Paul, you know more about Postscript than I do
> > > - is the problem that the PS file doesn't define any fonts?  Is this
> > > the way Metapost works? Does it work with dvips since the font will be
> > > already present in the `main' file?)
> > >
> > > If there's no way for xdvi to detect/fix this font problem, maybe we
> > > should switch to displaying a placeholder/bounding box for Metapost
> > > files - I don't know much about Metapost either; can we assume that
> > > files missing an `.(e)ps' extension are Metapost, or would we need
> > > to scan all files in 'PSfile' specials for a `%%Creator: MetaPost'
> > > comment?
> 
> metapost files are not .eps, although they're very close.  They require
> special processing, which I haven't implemented yet.  I should check what
> dvips does, and mimic that.

That, or whatever pdflatex uses to iterpret metapost files.

It would be great if you could fix this.

Thanks,

Chris