ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Werners-Lucchini" <wwl@musensturm.de>
To: ntg-context@ntg.nl
Subject: Re: MetaFont
Date: Fri, 17 Aug 2007 22:53:43 +0200	[thread overview]
Message-ID: <46C626F7.7918.22E524E@wwl.musensturm.de> (raw)
In-Reply-To: <mailman.999.1187335227.2346.ntg-context@ntg.nl>

> >>> But this does massivly restrict metafonts capabilities. Pens
> for
> >>> example are not allowed (Metafont with applied handbrake)!
> >> I agree, metatype1 is not very easy to use if you are familiar
> >> with
> >> metafont already. For existing fonts, mf2pt1 is in general the
> >> best
> >> approach, I think. There is a (patched?) version out there that
> >> delegates most the hard work to fontforge, and it's results are
> >> normally
> >> quite acceptable.
> > 
> > There was once (1990) an article in TUGboat 11:4, pages 525-541
> > which discribes an patch to mf84. The patched mf could produce
> type3 
> > fonts. Should'nt it be possible to do the same for type1?
> 
> Not without a lot of effort. Type3 fonts allow all sorts of stuff
> that is illegal in Type1, like overlapping and mixing of strokes
> and fills.

The cases where fontforge is refusing, are cases which are best 
handeld inside metafont, where one has the knowledge: a.) elliptical 
curves, which are represented by polygons (lots of points and 
resolution depandend) and should converted to something smoother, and 
b.) short epicycles, which are also artifacts from penmotions, which 
can easyly be detected and replaced by an corner point.

Wolfgang
___________________________________________________________________________________
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:[~2007-08-17 20:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.999.1187335227.2346.ntg-context@ntg.nl>
2007-08-17 20:53 ` Wolfgang Werners-Lucchini [this message]
     [not found] <mailman.925.1187183670.2346.ntg-context@ntg.nl>
2007-08-16  9:59 ` MetaFont Wolfgang Werners-Lucchini
2007-08-16 12:48   ` MetaFont Taco Hoekwater
     [not found] <mailman.916.1187162110.2346.ntg-context@ntg.nl>
2007-08-15 10:45 ` MetaFont Wolfgang Werners-Lucchini
2007-08-15 11:39   ` MetaFont Taco Hoekwater
     [not found] <mailman.859.1187098055.2346.ntg-context@ntg.nl>
2007-08-15  0:10 ` MetaFont Wolfgang Werners-Lucchini
2007-08-15  1:09   ` MetaFont Martin Schröder
2007-08-13 11:07 MetaFont Wolfgang Werners-Lucchini
2007-08-13 11:18 ` MetaFont Hans Hagen
2007-08-13 11:23   ` MetaFont Martin Schröder
2007-08-14 11:06   ` MetaFont Taco Hoekwater
2007-08-13 11:18 ` MetaFont Martin Schröder

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=46C626F7.7918.22E524E@wwl.musensturm.de \
    --to=wwl@musensturm.de \
    --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).