From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Small caps problem/bug with some fonts
Date: Sat, 19 Sep 2009 18:32:46 +0200 [thread overview]
Message-ID: <4AB507AE.9000501@wxs.nl> (raw)
In-Reply-To: <20090918220517.GA30581@crud.chemoelectric.org>
Barry Schwartz wrote:
> Hans Hagen <pragma@wxs.nl> skribis:
>> Barry Schwartz wrote:
>>
>>> If base mode uses the traditional TeX mechanism for ligatures, I don't
>>> see any way the font can be blamed.
>
> Ant does the same thing, I believe, using the OT tables and heuristics
> to run the TeX processor. That's okay, as long as the results aren't
> blamed on the font. :)
well, that's alway sa bit hard to determine, maybe not in this case but
there definitely are dubious cases and heuristics that works in one case
migh tfail in another; also, as context base mode is mostly meant for
simple cases (and as said, it might be wise in the case of snallcaps to
not enable ligatures) and therefore suits most cases, but as reference
(and for more advanced work) node mode has to be used ... actually, when
users report bugs with fonts i kind of assume node mode
in the perspective of the oriental tex project (related to luatex/mkiv)
a complex font is being made and quite some time goes into figuring out
what exactly the common ground in ot is (we've decided to settle for
uniscribe/volt for final decisions as that's the most advanced machinery)
for instance there are more combinations possible on otf than the font
generating programs can handle and some combinations are only handled by
some renderers. of course the mkiv machinery can be blamed for much, but
so can the specification itself, the font generating tools as wel as fonts
the best we can do is to try to deal with all but eventually i think
that i'll end up with a couple of extra features / checks / etc; there's
also already a patch mechanism in place
having more advanced fonts is nice, but unfortunately (for commercial
reasons, or for stability reasons or ...) font vendors have no real bug
fix and upgrade policy but at least i can fix my own bugs -)
btw, in most cases it helps to nail down problems when we have the font,
which not always is the case, so in such cases we might need to gamble
where the problem sits
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-09-19 16:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 12:57 Mika Ritola
2009-09-18 13:14 ` Hans Hagen
2009-09-18 17:35 ` Derek CORDEIRO
2009-09-18 17:54 ` Hans Hagen
2009-09-18 18:54 ` Derek CORDEIRO
2009-09-18 20:32 ` Barry Schwartz
2009-09-18 21:40 ` Hans Hagen
2009-09-18 22:05 ` Barry Schwartz
2009-09-19 16:32 ` Hans Hagen [this message]
2009-09-18 17:57 ` Hans Hagen
2009-09-18 20:35 ` Wolfgang Schuster
2009-09-18 18:01 ` Hans Hagen
2009-09-18 18:58 ` Derek CORDEIRO
2009-09-18 18:15 ` Barry Schwartz
2009-09-18 18:42 ` Hans Hagen
2009-09-18 20:19 ` Barry Schwartz
2009-09-18 21:39 ` Hans Hagen
2009-09-18 22:38 ` Barry Schwartz
2009-09-19 16:52 ` Hans Hagen
2009-09-22 4:15 ` Barry Schwartz
2009-09-22 7:18 ` Hans Hagen
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=4AB507AE.9000501@wxs.nl \
--to=pragma@wxs.nl \
--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).