From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to "unfill" a picture?
Date: Wed, 24 Jun 2009 11:02:45 +0200 [thread overview]
Message-ID: <4A41EBB5.6020609@elvenkind.com> (raw)
In-Reply-To: <769ba7780906240048x697498c3se024c67952dbca85@mail.gmail.com>
Zhichu Chen wrote:
> Cool, but just curiosity, metapost can handle fonts right?
> How those glyphs don't have this problem? I've read the
> specification of the type1 fonts, they don't seem to have
> such weird paths, just some borderlines with different
> directions.
PostScript paths are more advanced than Metapost's draw objects,
but Metapost never sees these paths of font glyphs at all.
(well, except via the new primitive 'glyph X of', but that
indeed does have this problem.)
Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-06-24 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 3:13 Zhichu Chen
2009-06-24 6:55 ` Zhichu Chen
2009-06-24 7:32 ` Taco Hoekwater
2009-06-24 7:48 ` Zhichu Chen
2009-06-24 9:02 ` Taco Hoekwater [this message]
2009-06-24 8:21 ` Wolfgang Schuster
2009-06-24 10:42 ` Zhichu Chen
2009-06-24 10:59 ` Zhichu Chen
2009-06-24 11:29 ` Hans Hagen
2009-06-24 11:42 ` Zhichu Chen
2009-06-24 14:12 ` Nicola
2009-06-24 14:45 ` Zhichu Chen
2009-06-25 5:15 ` Lutz Haseloff
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=4A41EBB5.6020609@elvenkind.com \
--to=taco@elvenkind.com \
--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).