![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
The MetaPost team is happy to announce a new release of MetaPost:
----------------------------------------------------------------------
MetaPost 1.204
----------------------------------------------------------------------
The standalone distribution package and a win32 binary can be downloaded
immediately from
http://foundry.supelec.fr/gf/project/metapost/
This release will also be available from CTAN soon, and it will be
included in the next TeXLive. The source package should compile normally
on all systems that are capable of compiling a modern web2c-based TeX
distribution.
The win32 binary is intended for texlive or a similar web2c-based
installation, this executable will *not* work for miktex.
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 MetaPost version 1.204:
----------------------------------------------------------------------
* Metapost could go into an endless output loop when characters in
bitmap fonts where used, because it tried to limit the %*Font output
line to a specific number of bytes.
----------------------------------------------------------------------
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 is free software: you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published
by the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
The MetaPost development project is currently hosted at Supelec,
http://foundry.supelec.fr/gf/project/metapost; please report bugs and
request enhancements through there if possible. Alternatively, you
can reach us through the