On Tue, Feb 15, 2005 at 01:00:03PM +0100, Frank K?ster wrote: > Stefan Ulrich <[EMAIL PROTECTED]> 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?)
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues implies that this is the case. > > > > 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? > > Shouldn't LaTeX indicate properly what it included? I don't guarantee that my example uses the correct way of including the metapost LaTeX - but if I've got it wrong, it wasn't obvious from the faq answers I've read -and it seemed to work in dvips. Chris PS Not directly relevant to the bug, but the molecular structures example at http://matagalatlante.org/nobre/featpost/doc/featexamples.html is the reason I'm using metapost. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
