ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Auto selecting optical sizes for a font
Date: Mon, 24 Jun 2013 19:50:01 +0200	[thread overview]
Message-ID: <51C886C9.6010304@wxs.nl> (raw)
In-Reply-To: <51C81647.3080105@gmail.com>

On 6/24/2013 11:49 AM, Georg Duffner wrote:
> Am 2013-06-24 10:27, schrieb Keith J. Schultz:
>
>> as such ConTexT should support the use of the size table in its font
>> handling,
>> but as Hans has mentioned design sizes a very special and few actually
>> know
>> what that information means and put it to a useful purpose.
>>
>> Question would be in far this font feature should be rudimentarily
>> supported.
>
> IMO, they should be fully supported. There are not so many fonts with
> that property and even less in the free software world, so one can
> assume that somebody possessing such font knows what that means and
> probably expects its support.

It doesn't change the fact that predictable font names (including 
weight, width, variant and modifier) are (and will remain) a mess so 
users need to know precisely what they ask for, even automatisms kick 
in. Ok, most users won't notice as dont definition files take care of 
loading, but in that case taking care of the designsizes can be hidden 
as well (which it is).

> I think, context should by default use the appropriate font for each
> font-size corresponding to the design range defined in the font’s table,
> while providing an interface to override that automatism.

Well, in that case we should also obey min/max specs that say that fonts 
cannot be used below or above certain sizes (and I found quite some that 
has such narrow ranges).

In the case of eb ... it's just a few entries in a goodie file, so that 
does the job. In pratice, finding a properly matched and sized monospace 
and math takes more time -)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2013-06-24 17:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1416.1372062425.2084.ntg-context@ntg.nl>
2013-06-24  9:49 ` Georg Duffner
2013-06-24 17:50   ` Hans Hagen [this message]
2013-06-25 21:16 Andres Conrado
  -- strict thread matches above, loose matches on Subject: below --
2013-06-25  4:16 Andres Conrado Montoya
2013-06-25  8:32 ` Hans Hagen
     [not found] <mailman.1409.1371913028.2084.ntg-context@ntg.nl>
2013-06-23 22:28 ` Georg Duffner
2013-06-24  8:02   ` Keith J. Schultz
2013-06-24 17:44     ` Hans Hagen
2013-06-24 17:42   ` Hans Hagen
2013-06-21 23:43 Andres Conrado Montoya
2013-06-22 12:04 ` Pablo Rodríguez
2013-06-22 12:07 ` 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=51C886C9.6010304@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).