ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: $n\choose k$-issue with OpenType math fonts
Date: Sun, 6 Mar 2011 12:03:04 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1103061159450.27552@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4D7375E5.7030805@wxs.nl>

On Sun, 6 Mar 2011, Hans Hagen wrote:

> On 6-3-2011 1:25, Andreas Harder wrote:
>> 
>> Am 04.03.2011 um 15:28 schrieb Hans Hagen:
>> 
>>> On 4-3-2011 2:09, Andreas Harder wrote:
>>>> Hi all,
>>>> 
>>>> I'm (re)tying to draw some attention to the $n\choose k$-issue with 
>>>> OpenType math fonts.
>>>> 
>>>> I've made some test files:
>>>> http://dl.dropbox.com/u/151837/OpenType-Math.7z
>>>> 
>>>> The best output is generated by LuaLaTeX (at least for Asana and 
>>>> Cambria). Would it be possible to correct the ConTeXt output as well?
>>> 
>>> It depends what correction boils down to. Normally it's the opentype font 
>>> parameters that control the threshold to the next step in a larger 
>>> delimiter
>> 
>> This subject is also discussed on the LuaLaTeX mailing list.
>> http://tug.org/pipermail/lualatex-dev/2011-March/thread.html#1118
>
> hm, i actually decided to limit the number of mailing lists to follow so best 
> provide a summary of conclusions instead of a link -)
>
> anyhow, I wonder if we really need to keep supporting this
>
>  x \operator y
>
> kind of syntax (at least that's what crossed my mind when i saw that this 
> atopwithdelims primitive was used in your example) .. maybe we should simply 
> define a few extra commands and relax these primitives

At the macro package level, I agree with this. The \over, \choose, \atop 
etc macros can be made \undefined; We already have a high level interface 
for them.

Do you also want to remove them from the engine? That will simplify the 
\mathstyle macros, but then luatex will not be backward compatible with 
tex. (I don't care about that, but others would).

> aditya: shouldn't we merge the m-newmath code into the core?

Definitely.

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
___________________________________________________________________________________


  parent reply	other threads:[~2011-03-06 17:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 13:09 Andreas Harder
2011-03-04 14:28 ` Hans Hagen
2011-03-04 20:47   ` Andreas Harder
2011-03-06  0:25   ` Andreas Harder
2011-03-06 11:54     ` Hans Hagen
2011-03-06 12:22       ` Andreas Harder
2011-03-06 14:33         ` Hans Hagen
2011-03-06 14:49           ` Andreas Harder
2011-03-13 14:01           ` Andreas Harder
2011-03-13 15:51             ` Aditya Mahajan
2011-03-13 16:01               ` Andreas Harder
2011-03-06 17:03       ` Aditya Mahajan [this message]
2011-03-06 17:56         ` 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.01.1103061159450.27552@ybpnyubfg.ybpnyqbznva \
    --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).