ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: metapost@tug.org,  ntg-context@ntg.nl,  metafont@ens.fr,
	 TeX Implementoren <tex-implementors@tug.org>,
	"MetaPost bug reports and discussion." <mp-implementors@tug.org>
Subject: MetaPost 1.003 announcement
Date: Thu, 10 Apr 2008 15:45:07 +0200	[thread overview]
Message-ID: <47FE19E3.9090004@elvenkind.com> (raw)


The MetaPost team is happy to announce a new release of MetaPost:

----------------------------------------------------------------------
MetaPost 1.003
----------------------------------------------------------------------

The sources and a win32 package can be downloaded immediately from

   http://foundry.supelec.fr/projects/metapost/

The source package should compile normally on all systems that are
capable of compiling a modern web2c-based TeX distribution.

The win32 package is intended for texlive or a similar web2c-based
installation, and has been tested only with TeXLive 2007. These
executables will *not* work for miktex, sorry.

Of course, we welcome any comments (either good or bad) that you may
have. Simply replying to this message is fine, but see the bottom of
the message for a more formal way to report bugs and feature requests.

----------------------------------------------------------------------
What is new in version 1.003:
----------------------------------------------------------------------

* Polygonal pens now work better (bug #3 and #7 at supelec.fr).

* When asking for a color part in a picture object, the color models
   now have to match each other, otherwise an error will be reported
   and the return value will be set to a 'black' part.

* The Makefile fragment (metapost.mk) now defines a separate mpost
   target for better integration in TeXLive.

* There was a bug in the internal handling of withprescript and
   withpostscript, resulting in incorrect output when paths using
   such scripts were stored in picture variables.

* A newline was missing from the PostScript output when the
   procset internal variable was set, so the first line of that
   accidentally became a PostScript comment.

* Applicable changes from Knuth's updates for MetaFont 2.718281
   are incorporated.

* Mpto did not play nice with %&<format> verbatimtex lines, it now
   automatically tries to detect comment-lines.

* Dvitomp  1.003 has higher limits for some internal constants like
   the number of allowed fonts in DVI files.

* The manual is improved.


----------------------------------------------------------------------
Legal notice / license / bug reports
----------------------------------------------------------------------
MetaPost is a system for producing graphics developed by John Hobby
at AT&T, based on Donald Knuth's Metafont.  The MetaPost home page
is http://tug.org/metapost.

MetaPost and related programs are in the public domain.

The MetaPost development project is currently hosted at Supelec,
https://foundry.supelec.fr/projects/metapost; please report bugs and
request enhancements through there if possible. Alternatively, you
can reach us through the <metapost@tug.org> mailing list as well.

Have fun!

Taco Hoekwater, for the MetaPost team, April 10, 2008.




___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


                 reply	other threads:[~2008-04-10 13:45 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=47FE19E3.9090004@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=metafont@ens.fr \
    --cc=metapost@tug.org \
    --cc=mp-implementors@tug.org \
    --cc=ntg-context@ntg.nl \
    --cc=tex-implementors@tug.org \
    /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).