From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Averaged integrals
Date: Mon, 14 Apr 2014 10:22:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.03.1404141021000.13261@hzvpu.rqh> (raw)
In-Reply-To: <877g6sc852.fsf@approx.mit.edu>
On Mon, 14 Apr 2014, Sanjoy Mahajan wrote:
> Janne Junnila <janne.junnila@gmail.com> writes:
>
>> On a related note: It seems to me that \ointclockwise and
>> \ointctrclockwise produce results opposite to what their names would
>> indicate.
>
> It seems wrong to me as well. It could be a problem in a mapping
> internal to context (or maybe the font). char-def.lua gives, for
> example,
>
> [0x2232]={
> category="sm",
> description="CLOCKWISE CONTOUR INTEGRAL",
> direction="on",
> linebreak="al",
> mathclass="limop",
> mathname="ointclockwise",
> unicodeslot=0x2232,
> },
>
> The Unicode slot number is correct. If you look up that Unicode character
>
> <http://www.fileformat.info/info/unicode/char/2232/index.htm>
>
> it has a clockwise arrow. But, as you say,
>
> \starttext
> $\ointclockwise$
> \stoptext
>
> shows an anticlockwise arrow.
I get clockwise arrow with cambria and xits, but anticlockwise arrow with
palatino and latin modern. So, it appears to be a font bug with TeX Gyre
fonts.
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:[~2014-04-14 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 14:03 Janne Junnila
2014-04-14 14:12 ` Sanjoy Mahajan
2014-04-14 14:22 ` Aditya Mahajan [this message]
2014-04-14 14:53 ` 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.03.1404141021000.13261@hzvpu.rqh \
--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).