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: Boguslaw Jackowski <b_jackowski@gust.org.pl>
Subject: Re:  math: ± and ∓  are shifted
Date: Fri, 05 Apr 2013 09:32:51 +0200	[thread overview]
Message-ID: <515E7E23.4090804@wxs.nl> (raw)
In-Reply-To: <20130405001601.GA24908@khaled-laptop>

On 4/5/2013 2:16 AM, Khaled Hosny wrote:
> On Fri, Apr 05, 2013 at 12:55:40AM +0200, Hans Hagen wrote:
>> On 4/5/2013 12:13 AM, Aditya Mahajan wrote:
>>> On Fri, 5 Apr 2013, Hans Hagen wrote:
>>>
>>>> On 4/4/2013 11:44 PM, Aditya Mahajan wrote:
>>>>> On Thu, 4 Apr 2013, Xenia wrote:
>>>>>
>>>>>> Hi context list,
>>>>>>
>>>>>> I noticed that the ∓ sign is a little higher than the ± sign, so that
>>>>>> the + signs are at the same height. But this looks strange and
>>>>>> should be
>>>>>> changed.
>>>>>
>>>>> Indeed. These look very odd. I tested this with cambria and the outcome
>>>>> is similar, so this is not a font bug, but something wrong in ConTeXt's
>>>>> math handling.
>>>>
>>>> I'm not sure if I understand the issue
>>>>
>>>> - lm has + and - touching with the + in the same position as the
>>>> regular +
>>>>
>>>> - cambria has a gap between + and - and moves the + up and down
>>>>
>>>> Afaik context isn't doing any magic here as these are precomposed
>>>> glyphs that directly map.
>>>>
>>>> $a \ruledhbox{$+$} b \ruledhbox{$-$} c$
>>>>
>>>> $a \ruledhbox{$±$} b \ruledhbox{$∓$} c$
>>>>
>>>> they are 'binary' in math mode, just like + and -
>>>
>>> The question is not about the shape of the glyph, but their location.
>>> But after looking at the output of latex for CM and Cambria, I am no
>>> longer sure what the correct output should be. For Cambria, ConTeXt and
>>> LaTeX give similar outputs. For CM/LM they give different outputs.
>>
>> it looks like the open type version has a fitting boundingbox while
>> the type 1 variants have a bit of the + sticking out:
>
> CFF fonts do not store bounding box info anywhere, the engine just
> calculates it based on glyph outlines. For TFM fonts the metrics can be
> adjusted to achieve specific alignment.

Sure, but one can 'cheat' with the boundingboxes as they're not cropboxes.

It's no big deal to adapt some metrics in mkiv, but best have the font 
do the job.

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-04-05  7:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 21:36 Xenia
2013-04-04 21:44 ` Aditya Mahajan
2013-04-04 22:06   ` Hans Hagen
2013-04-04 22:13     ` Aditya Mahajan
2013-04-04 22:55       ` Hans Hagen
2013-04-05  0:16         ` Khaled Hosny
2013-04-05  7:32           ` Hans Hagen [this message]
2013-04-05 13:46             ` 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=515E7E23.4090804@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=b_jackowski@gust.org.pl \
    --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).