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>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Fwd: Re:  New beta 2010-09-22 and xits fonts
Date: Sun, 26 Sep 2010 13:05:21 +0200	[thread overview]
Message-ID: <4C9F28F1.7020606@wxs.nl> (raw)
In-Reply-To: <4C9EFD16.60408@elvenkind.com>

On 26-9-2010 9:58, Taco Hoekwater wrote:
> On 09/25/2010 09:00 PM, Khaled Hosny wrote:
>>>
>>> Many thanks Hans: now xits fonts work as before (with ConTeXt ver:
>>> 2010.09.24 11:40 MKIV fmt: 2010.9.24).
>>> However, for some reason it seems that the white space (or should I
>>> say the glue?) between some operators such as \int and the following
>>> characters is too big.
>>
>> Seems like another italic correction related issue. Taco, should the
>> italic correction be ignored if the \int does not have scripts?
>
> This gets sort of ridiculous, as *ignoring* the italic correction is not
> good enough, it has to be explicitly substracted from the glyph width
> (at least that is the case for the integrals with subscripts so I
> assume that that will apply here as well). Why on earth would someone
> design a font in this manner ?!
>
> Anyway, a small test file would be helpful, as it should not be hard
> to do. Can you create a tracker?

is this to be hardcoded or do we need flags for that so that we can set 
the method depending on the font .. implementing redicoulous specs 
sounds somewhat strange

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:[~2010-09-26 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25 16:07 Hans Hagen
2010-09-25 16:32 ` Andreas Harder
2010-09-25 19:00 ` Khaled Hosny
2010-09-26  7:58   ` Taco Hoekwater
2010-09-26 11:05     ` Hans Hagen [this message]
2010-09-26 11:26       ` Khaled Hosny

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=4C9F28F1.7020606@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /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).