ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: unicode integral sign
Date: Sat, 29 May 2010 20:57:22 +0200	[thread overview]
Message-ID: <4C016392.9070809@elvenkind.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1005291315320.13102@ybpnyubfg.ybpnyqbznva>

Aditya Mahajan wrote:
> On Sat, 29 May 2010, Yury G. Kudryashov wrote:
> 
>> Taco Hoekwater wrote:
>>
>>> Yury G. Kudryashov wrote:
>>>> Hi!
>>>>
>>>> I try the following:
>>>>
>>>> \starttext
>>>> $∫_a^b \int_a^b$
>>>> \stoptext
>>>>
>>>> In the first case, the integral sign is below the text. Should I use
>>>> another font, or is it possible to fix with the default one?
>>>
>>> It is possible to fix this. The reason for the odd placement is that the
>>> 'math code' of ∫ is not set up properly (and it probably isn't either
>>> for some other bare Unicode characters). To fix the hard way, add this
>>> at the top of your input file:
>>>
>>> \Umathcode `∫ = 1 0 `∫ % 1 == \mathop, 0=fam0, ∫=glyph
>> Is there any documentation on char-def.lua file format? If I'll 
>> understand it, I'll send a patch for the symbols I use.
> 
> Not a complete documentation, but some explanation is here
> 
> https://www.tug.org/members/TUGboat/tb30-2/tb95mahajan-cmath.pdf
> 
>> Currently I have no idea why the following strings in char-def don't 
>> work.
>>
>> [0x222B]={
>>  adobename="integral",
>>  category="sm",
>>  cjkwd="a",
>>  description="INTEGRAL",
>>  direction="on",
>>  linebreak="ai",
>>  mathspec={
>>    { class="nothing", name="intop" },
>>    { class="limop"  , name="int"   },
>>  },
>>  unicodeslot=0x222B,
>> },
>>
>> Replacing mathspec=... with mathclass="limop", mathname="int" seems to 
>> work (copied from n-ary summation).
>>
>> BTW, in both solution ∫_a acts like \int\limits_a, not \int_a.
> 
> In plain TeX, this is taken care by
> 
> \mathchardef\intop="1352 \def\int{\intop\nolimits}
> 
> Can I do the same in luatex without active characters?

No, but it is a useful extension to consider. There are internally
three types of large operators, for 'limits', 'nolimits' and
'displaylimits' and this bothers me a bit. We can't reasonably
extend the old primitives, but \Umathcharcode c.s. could be made
to accept extra values '9' .. '11' for those three types without
any compatibility problems.  I'll add to the tracker.

Best wishes,
Taco


___________________________________________________________________________________
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-05-29 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29  7:45 Yury G. Kudryashov
2010-05-29  9:58 ` Taco Hoekwater
2010-05-29 15:21   ` Yury G. Kudryashov
2010-05-29 17:32     ` Aditya Mahajan
2010-05-29 18:57       ` Taco Hoekwater [this message]
2010-05-29 19:05         ` Aditya Mahajan

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=4C016392.9070809@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).