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: Sat, 19 Sep 2009 18:52:54 +0200	[thread overview]
Message-ID: <4AB50C66.7080805@wxs.nl> (raw)
In-Reply-To: <20090918223847.GB30581@crud.chemoelectric.org>

Barry Schwartz wrote:
> Hans Hagen <pragma@wxs.nl> skribis:
>> 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)
> 
> Yeah, I think trying to be fancy with contextual substitutions is a
> bit like getting drunk. I'm not even sure why there was a "frac" tag
> when it was originally intended to be converted to "numr" and "dnom"
> tags.
> 
> (I just looked at
> http://www.microsoft.com/typography/otspec160/features_fj.htm#frac
> to see what it says nowadays and now want to go get drunk.)

actually the frac featurs, like most features is a rather generic one 
and as such it should work out of the box (some of the justitication 
features use gpos and/or assume specific renderer support, and some of 
that is rather undefined)

so, its not that frac itself is the problem dealing with in the engine, 
because if so, many features would be a problem, it's just that font 
makers stick to a couple of simple rules like:

(1) replace all
       <digits> <slash> <digits>
     by
       <sup digits> <overlapping frac slash> <sub digits>

(1) replace all
       <digits> <slash> <digits>
     by
       <sup digits> <overlapping frac slash> <sub digits>

and if they have rule 2, it will mess up things like a/b

of course it can be properly dealt with ... just make proper rules

now, one reason that metafont kind of design tools never were accepted 
as basic tool for font design is that designers are no programmers; and 
one needs programmers (or at least some of the related mindset) to make 
the more complex ot fonts (or one needs teams)

actually, as many fonts do have the sup/sub digits its rather trivial to 
provide proper frac's in mkiv but till now i had no reason (time, 
project, etc) for doing it

i fear the moment when designers start giving me rules like "use this or 
that font and turn on those features" assuming dtp like control and 
tweaking of the text (one reason for spending much time on fonts in mkiv 
is that it will give me control over bad behaving fonts; think of wrong 
glyph to unicode mapping and such)



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-19 16:52 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
2009-09-18 22:38           ` Barry Schwartz
2009-09-19 16:52             ` Hans Hagen [this message]
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=4AB50C66.7080805@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).