From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl, taco@elvenkind.com
Subject: Re: bug or feature? aer font problems
Date: Wed, 20 Jun 2001 17:29:34 +0200 [thread overview]
Message-ID: <3.0.6.32.20010620172934.009f7790@server-1> (raw)
In-Reply-To: <200106201435.QAA29628@sol.cs.uni-dortmund.de>
At 04:35 PM 6/20/01 +0200, Patrick Gundlach wrote:
>Hi,
>
>is this a bug or a feature???
>ConTeXt ver: 2001.4.9 fmt: 2001.6.20 int: english mes: english
>
>
>\setupbodyfont[cmr]
>\type{--}
>\setupbodyfont[aer]
>\starttext
>\type{--}
>\setupbodyfont[cmr]
>\type{--}
>\stoptext
A bug since one expects to see --
strange problem, maybe there is a -- lig in the aer ttfonts (which is a bug
then in aer). Maybe taco knows?
btw, since cmr and aer and scr and plr share some things, you should be
aware of filename remapping as is doen in aer def's. So, this is why the
second cmr stays aer: cmr10 has become aer10 and there is no way back.
In the new font layer, you can do more tricky things and create typeface
sets so that real weird mixes are possible [all have their own namespace].
So far my tests work out ok, tso i will release soon. [also faster, i now
run my complicated test file over twice as fast as a couple of months ago].
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-06-20 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 14:35 Patrick Gundlach
2001-06-20 15:29 ` Hans Hagen [this message]
2001-06-22 23:24 ` Uwe Koloska
2001-06-20 15:00 Patrick Gundlach
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=3.0.6.32.20010620172934.009f7790@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.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).