From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Small integral signes with Palatino
Date: Thu, 24 May 2012 18:40:25 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1205241818230.28662@qrpragenyvmrq> (raw)
In-Reply-To: <CALBOmsZ19F6B9=gEHZthH=QffOCQ6sE8QE-+=r8VwpPOp2Fcsg@mail.gmail.com>
On Fri, 25 May 2012, Mojca Miklavec wrote:
> On Fri, May 25, 2012 at 12:05 AM, Mojca Miklavec wrote:
>> On Thu, May 24, 2012 at 3:59 PM, Aditya Mahajan wrote:
>>>
>>> Any idea when this was introduced (or if this bug was always present)?
>>
>> beta 2011.07.14 16:09
>
> Oh, I'm sorry, nonsense. That was the last working one. The one
> introducing the bug was
> 2011.07.19 10:35
>
> https://github.com/mojca/context/commit/a3f9fa299ecc3c9d8c3989c6e219dd9a1bcefaa1
>
> In that version the functionality was completely broken (overlapping
> limits), then it improved with time a bit, but never recovered
> properly back.
I tested with asana, hoping that opentype fonts will behave better, but
asana is hopelessly broken in the other direction: too big integrals and
sums. To fix asana, change
DisplayOperatorMinHeight = more,
to
DisplayOperatorMinHeight = 0,
(or just comment it) in asana-math.lfg. After that, you can at least use
asana math as a work around.
Euler and Stix fonts work OK, and surprisingly so is txfonts! I thought
that px- and tx-fonts were handled identically. Why does the bug only
appear with px-fonts?
Comparing the two files, I noticed that skewchar is not set in px fonts.
Line 22 of px-math.lfg should be:
{ name = "texgyrepagella-bold.otf", vector = "tex-bf", skewchar=0x7F } ,
(but even after that change $\hat {\bi A}$ is set incorrectly).
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-24 22:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 10:52 Tim Steenvoorden
2012-05-24 8:05 ` Tim Steenvoorden
2012-05-24 8:09 ` luigi scarso
2012-05-24 13:59 ` Aditya Mahajan
2012-05-24 21:40 ` Tim Steenvoorden
2012-05-24 22:05 ` Mojca Miklavec
2012-05-24 22:13 ` Mojca Miklavec
2012-05-24 22:39 ` Hans Hagen
2012-05-24 22:43 ` Aditya Mahajan
2012-05-25 8:55 ` Hans Hagen
2012-05-27 15:16 ` Tim Steenvoorden
2012-05-27 15:31 ` luigi scarso
2012-05-27 17:50 ` luigi scarso
2012-05-27 23:16 ` luigi scarso
2012-05-27 23:27 ` Aditya Mahajan
2012-05-28 1:29 ` Steve Peter
2012-05-29 8:43 ` Herbert Voss
2012-05-29 9:04 ` Tim Steenvoorden
2012-05-29 9:15 ` Tim Steenvoorden
2012-05-28 5:27 ` Mojca Miklavec
2012-05-28 12:50 ` Hans Hagen
2012-05-24 22:40 ` Aditya Mahajan [this message]
2012-05-24 23:13 ` Hans Hagen
2012-05-25 2:17 ` Khaled Hosny
2012-05-25 8:55 ` 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=alpine.LNX.2.02.1205241818230.28662@qrpragenyvmrq \
--to=adityam@umich.edu \
--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).