From: Mojca Miklavec <mojca.miklavec1@email.si>
Subject: Re: Vector or bitmapped?
Date: Sat, 13 Nov 2004 22:44:07 +0100 [thread overview]
Message-ID: <41968027.9070203@email.si> (raw)
In-Reply-To: <200411131423.18663.john@wexfordpress.com>
John Culleton wrote:
> After generating a graphic via Metapost and Metafun, is the result a vector
> graphic or a bitmapped graphic?
The resulting PDF is a vector graphic of course.
(But if you need a bitmapped one, you can create it any time of course;
if not with 'printscreen', than with
pdftops -eps img
gs -bSAFER -dBATCH -bNOPAUSE -dGraphicsAlphaBits=4 -r100 \
-sDEVICE=png16m -sOutputFile=img.png img.eps)
Mojca
PS:
Willi Egger wrote:
> Metapost generates postscript.
(The original output format of metapost is really postscript, but if you
use btex...etex or textext, you have to process the plain metapost files
with 'mp img' and then with 'mptopdf img' in order to get the TeX labels
typeset correctly; if you use it within ConTeXt, the output format is
PDF anyway.)
prev parent reply other threads:[~2004-11-13 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 19:23 John Culleton
2004-11-13 20:42 ` Willi Egger
2004-11-13 21:44 ` Mojca Miklavec [this message]
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=41968027.9070203@email.si \
--to=mojca.miklavec1@email.si \
--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).