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:42:07 +0200	[thread overview]
Message-ID: <51C884EF.7080503@wxs.nl> (raw)
In-Reply-To: <51C77673.1010606@gmail.com>

On 6/24/2013 12:28 AM, Georg Duffner wrote:
> Am 22.06.2013 16:57, schrieb Hans Hagen:
>
>> We have no feature 'size' (or I must have forgotten about it). As
>> there is no consistency in designsizes and there is always some
>> esthetic choice involved no automatic mechanism is (and will be)
>> build in.
>
> Hi,
>
> There is a 'size' table in opentype fonts which contains informations
> about the design size, the design range and a style-ID and -name. Fonts
> that come with different optical sizes do in fact use that table exactly
> for the purpose desired by Andrés. Latin Modern does so, Adobe fonts do
> so and EB Garamond happens to use that table too. XeLaTeX and LuaLaTeX
> interpret it correctly (by means of fontspec, IIRC). So perhaps it’s
> worth reconsidering this.

It's too much trouble for the few fonts that come in design sizes. As 
typescripts need to be defined adding the bit of extra info is no 
problem. I had a look at the relevant info and in order to make it work 
with the context font loader (the name driven one, as for files it is 
irrelevant anyway) quite some fuzzy logic has to be applied: we need a 
proper way (at least in context) to identify regular, italic, bold 
italic etc combined with the font name and the fact that names (as well 
as modifiers) are poluted makes that for lm a different logic has to be 
applied than for eb and if I don't do some filtering we get an 
inconsistent lot of of antykwas being seen as a design size collection 
as well.  I just tried to make a an auto-internal-goodie generator and 
some tracing showed me that if we can get 50% done right, we need to 
work around the other 50%. (I have lots of fonts on my system).

So for the moment I'll stick to providing goodies files. After all, 
users load a relevant typescript anyway so much gets hidden. If we get 
dozens of design sized files I'll look into it again.

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
___________________________________________________________________________________

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [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.1416.1372062425.2084.ntg-context@ntg.nl>
2013-06-24  9:49 ` Georg Duffner
2013-06-24 17:50   ` 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=51C884EF.7080503@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).