From: tlaronde@polynum.com (tlaronde at polynum.com)
Subject: [9fans] [survey] mp or mpost? (MetaPost)
Date: Sun, 20 Mar 2011 21:11:59 +0100 [thread overview]
Message-ID: <20110320201159.GA7350@polynum.com> (raw)
Hello,
I'm finishing the integration of John Hobby's MetaPost to kerTeX.
Since MetaPost can work with either some instance of TeX or troff for
formatting labels included in the figures, it can be of general use even
for troff only users.
So the question:
MetaPost was first named (for plain format) mp(1) but renamed mpost(1)
since there was a mp(1) PostScript formatting program (on Solaris
initially, if I'm not mistaken).
Is this later program still of wide use (seems not touched since 2002)?
I'm rather inclined to give MetaPost "its" name back, so mp(1).
By the way (more for John Hobby), the torture test will be given a
distinct name: twist (trip is for TeX; trap is for METAFONT).
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
reply other threads:[~2011-03-20 20:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110320201159.GA7350@polynum.com \
--to=tlaronde@polynum.com \
/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).