ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Fri, 18 Sep 2009 23:39:23 +0200	[thread overview]
Message-ID: <4AB3FE0B.2060406@wxs.nl> (raw)
In-Reply-To: <20090918201908.GA29031@crud.chemoelectric.org>

Barry Schwartz wrote:

> The font is unambiguous about it, though. Are you sure the software
> isn't performing the feature list in order rather than lookup list? Or
> is the software performing substitutions in its own ad hoc order?

in basemode we use built in traditional tex methods, so only ligatures 
and kerning; as a bonus i also support replacements, but in base mode 
the user really has to know what he/she asks for; in thsi particular 
case, asking for both ligatures (not contextual btw) and repacements 
(smsc) one gets them combined

so, this is why there is (the somewhat slower but more conforming) node 
mode as well; in that case (contextual) lookups are taken care of

but even then, if a font is not clear about issues, then one can get 
unwanted side effects (the frac feature for instance is often quite 
bugged and can only be applied selectively)

also, in context mkiv we have variants like dynamic features, user 
defined features, strategies etc (after all, nothing can stop us from 
doing a better job)

> Now I _make_ opentype fonts with small caps and ligatures and so want
> the software to do what I tell it (except when it was I who made the
> error).  :)

well, as said ... base mode has some known limitations and if you want 
the whole lot, you should use node mode (fyi: apart from isolated 
features we also support mixtures; the open type font format makes no 
assumptions about tags and gpos/gsub application so for instance the 
smallcaps feature might use one-to-one subsititutions as well as any 
other kind and complex fonts (like idris arabic font) does that)

(maybe simplefonts should default to node mode)

Hans

ps. if you run (as i demonstrated at the eurotex/context conference)

mtxrun --script server --auto

you can access an interactive features tester in your webbrouwser

there is also a trace option there where you can see what happens (in 
node mode)

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
___________________________________________________________________________________


  reply	other threads:[~2009-09-18 21:39 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
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 [this message]
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=4AB3FE0B.2060406@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).