From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/53021 Path: news.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Small caps problem/bug with some fonts Date: Sat, 19 Sep 2009 18:32:46 +0200 Message-ID: <4AB507AE.9000501@wxs.nl> References: <86d68cc30909180557x19dea6b8o8a2562f125a85275@mail.gmail.com> <4AB387A0.2000300@wxs.nl> <33c64e670909181035u4b766efesd85c99aeb566adbc@mail.gmail.com> <4AB3C963.7010102@wxs.nl> <33c64e670909181154u231cef8bk3044ce2f0f8b809a@mail.gmail.com> <20090918203238.GA29347@crud.chemoelectric.org> <4AB3FE66.1020005@wxs.nl> <20090918220517.GA30581@crud.chemoelectric.org> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1253378003 10066 80.91.229.12 (19 Sep 2009 16:33:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 19 Sep 2009 16:33:23 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Sat Sep 19 18:33:16 2009 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by lo.gmane.org with esmtp (Exim 4.50) id 1Mp2s7-0007tj-SD for gctc-ntg-context-518@m.gmane.org; Sat, 19 Sep 2009 18:33:15 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 77E9AC9A90; Sat, 19 Sep 2009 18:33:11 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id akVuKO83uol3; Sat, 19 Sep 2009 18:33:11 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id C16BAC9A92; Sat, 19 Sep 2009 18:33:06 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 39BECC9A81 for ; Sat, 19 Sep 2009 18:32:50 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rYH3iyqh8+JE for ; Sat, 19 Sep 2009 18:32:47 +0200 (CEST) Original-Received: from mail.pragma-ade.net (dsl-083-247-100-017.solcon.nl [83.247.100.17]) by balder.ntg.nl (Postfix) with ESMTP id 1A40FC9A92 for ; Sat, 19 Sep 2009 18:32:45 +0200 (CEST) Original-Received: from [10.100.1.100] (unverified [10.100.1.100]) by controller-1 (SurgeMail 3.9e) with ESMTP id 9402-1840426 for ; Sat, 19 Sep 2009 18:32:45 +0200 User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) In-Reply-To: <20090918220517.GA30581@crud.chemoelectric.org> X-Originating-IP: 10.100.1.100 X-Authenticated-User: hagen@controller-1 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:53021 Archived-At: Barry Schwartz wrote: > Hans Hagen 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 ___________________________________________________________________________________