From: Ron van Ostayen <R.A.J.vanOstayen@WbMT.TUDelft.NL>
Subject: Re: Greek characters in metapost
Date: Fri, 13 Sep 2002 09:32:50 +0200 [thread overview]
Message-ID: <3D8194A2.9090102@WbMT.TUDelft.NL> (raw)
In-Reply-To: <20020913021250.591cdf54.morawski@gmx.net>
Jens-Uwe Morawski wrote:
> On Thu, 12 Sep 2002 22:27:35 +0200
> Ron van Ostayen <R.A.J.vanOstayen@WbMT.TUDelft.NL> wrote:
>
>
>>Jens-Uwe Morawski wrote:
>>
>>>The PostScript file is not self-contained, i.e. no fonts
>>>are included. Therefore the figure has to be embedded in
>>>a ConTeXt document (\externalfigure)
>>>
>>
>>This is true, however, I want to have a self-contained postscript file,
>>or rather, a postscript file I can include in a *LaTeX* document. (I
>>know this is the ConTeXt-list but I expected to find a lot of MetaPost
>>experts on this list. :-))
>>
>
> If you embed the MP-output test.0 in your LaTeX document using
> \includegraphics of the graphicx package, then the output
> should show the \alpha. Depending, whether you are using pdflatex
> or latex, pdflatex itself or dvips include the appropriate fonts
> and encodings.
>
> Try the following LaTeX file with pdflatex. It should show the \alpha.
It does. Thanks Jens.
There is a small difference in the header between the PS-files produced by:
mpost --tex=latex test.mp
and
texexec --mptex test.mp
If I include the PS-picture from the 1st command in a latex file and
produce a PS file using:
latex test
dvips test -o test.ps
then the resulting PS-file *doesn't* show the \alpha
The PS-picture from the 2nd command *does*.
Any idea what causes this difference?
Ron
next prev parent reply other threads:[~2002-09-13 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 11:15 Ron van Ostayen
2002-09-12 14:19 ` Jens-Uwe Morawski
2002-09-12 20:27 ` Ron van Ostayen
2002-09-13 0:12 ` Jens-Uwe Morawski
2002-09-13 7:32 ` Ron van Ostayen [this message]
2002-09-14 7:35 ` Henning Hraban Ramm
2002-09-14 9:15 ` Greek characters in metapost (solution) Ron van Ostayen
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=3D8194A2.9090102@WbMT.TUDelft.NL \
--to=r.a.j.vanostayen@wbmt.tudelft.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).