ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Fabrice Couvreur <fabrice1.couvreur@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: integral symbol
Date: Thu, 29 Dec 2016 12:12:20 +0100	[thread overview]
Message-ID: <CACyK-eqHTg=s_v_Pktt2yQ+M04icM6+0AsLkWZJ+hzTY-WaYTw@mail.gmail.com> (raw)
In-Reply-To: <8cc55f4b-02dd-c35a-e48a-ae9326226c68@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 2982 bytes --]

Hi Hans,
Thanks for your solution. I created a macro, is it "robust" ?
Fabrice

\setupmathextensible[integral][rightoffset=-3mu,exact=yes,factor=2]
\def\integ#1#2#3{\math{\autointegral{#1}{#2}{#3}\diff x}}

\starttext
 \integ{4}{1}{g(x)}
\stoptext


2016-12-28 18:40 GMT+01:00 Hans Hagen <pragma@wxs.nl>:

> On 12/28/2016 6:14 PM, Alan Braslau wrote:
>
>> Hi Hans, Hi list,
>>
>> This is similar to what we have discussed earlier on this list and
>> elsewhere regarding \over vs. \frac. (I agree with Knuth that {a \over
>> b} is *much* more readable in running source code than \frac{a}{b} but
>> have resigned myself to use \frac{}{}, as this can be made better
>> behaved and gives a much better result.)
>>
>> Other traditional TeX constructs like \int^a_b have their charm (and
>> need to remain supported, just like is \over), but I support
>> introducing and encouraging the use of new constructs like your example
>> below. An alternative syntax (that could co-exist) would be admitting
>> $\left\int ... \right.$, but I do not know what limitations there might
>> be with both the (luatex) engine and with ConTeXt.
>>
>
> the tricky part there is that int has super and subscripts while left /
> right are different animals ... i looked into this (in the engine) and
> decided to delay implementing that (i might do it some day but it's sort of
> tricky to keep compatibility)
>
> also, ints are upright (extensible or stepwise sizes) or slanted (stepwise
> sizes) so even if we support something there are some limitations due to
> lack of font support (could be dealt with in due time)
>
> The problem with extensions, like always, in straying from traditional
>> TeX is interchangeability of code, or, more importantly, in the
>> learning curve obstacles that this introduces to traditional TeX (and
>> LaTeX) thinking. I know that at some level we do not care, for we often
>> make (good) design choices that improve the syntax of ConTeXt.
>>
>> Perhaps we can use this thread to discuss other cases (like \sum, ...)
>> that present difficulties and then decide on good solutions.
>>
>
> sure ...
>
> Hans
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>        tel: 038 477 53 69 | www.pragma-ade.nl | 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/list
> info/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
> ____________________________________________________________
> _______________________
>

[-- Attachment #1.2: Type: text/html, Size: 5310 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-12-29 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28 10:39 Fabrice Couvreur
2016-12-28 11:19 ` Henri Menke
2016-12-28 13:02   ` Fabrice Couvreur
2016-12-28 16:42     ` Hans Hagen
2016-12-28 17:14       ` Alan Braslau
2016-12-28 17:40         ` Hans Hagen
2016-12-29 11:12           ` Fabrice Couvreur [this message]
2016-12-29 12:06             ` 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='CACyK-eqHTg=s_v_Pktt2yQ+M04icM6+0AsLkWZJ+hzTY-WaYTw@mail.gmail.com' \
    --to=fabrice1.couvreur@gmail.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).