From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Reg. fonts and math
Date: Sat, 14 Jan 2006 03:36:14 -0500 (EST) [thread overview]
Message-ID: <Pine.WNT.4.63.0601140334040.2476@nqvgln> (raw)
In-Reply-To: <Pine.WNT.4.63.0601131951280.732@nqvgln>
<--- On Jan 13, Aditya Mahajan wrote --->
> <--- On Jan 13, Hans Hagen wrote --->
>
>> Aditya Mahajan wrote:
>>
>>> No, I mean the complicated math is much harder in context. Consider
>>>
>>> \begin{align}
>>> a &= b \\
>>> c &= d \notag \\
>>> &= f \notag \\
>>> &= g
>>> \end{align}
>>>
>>> which will typeset as
>>>
>>> a = b (1)
>>> c = d
>>> = f
>>> = g (2)
>>>
>>> \begin{subequations}
>>> \begin{align}
>>> a &= b \\
>>> c &= d
>>> \end{align}
>>> \end{subequations}
>>>
>>> Compare this from how to do this in context (see the wiki). You have to
>>> *manually* set the number of the subequation. Actually, for equation
>>> numbering and refering, the context way is rather limited. Consider
>>> something like an align environment
>>>
>>> a &= b\\
>>> c &= d\\
>>> e &= f
>>>
>>> Suppose, I want to refer to the second equation. In latex, I can simply
>>> add \label{eq:2} and the end of c&= d and then \ref{eq:2}. For context,
>>> the reference label goes at the top, with \placeformula[eqs]. But I am not
>>> sure, how to give individual labels to each equations.
>>
>> this 'loose label' is one of the ugliest concept i can think of -)
>
> If you come up with any other way, I will be glad to use it. Frankly, I do
> not think that the latex syntax is the best, but plain tex looks too
> indimidating and context does not have anything yet.
>
>> btw, defaulting to numbers and then using \notag is messy; i prefer
>> readable code, even if it takes more bytes; inventing a formula takes
>> more time than keying it in. Also, more structure, means more hooks for
>> configurability
>
> Fine by me. Your method is perfectly acceptable.
>
>> much if this 'complicated' math is not that complicated to support,see
>> attached file
>
> Wonderful. I did not know that something like this can be done so easily in
> context.
>
>> i'm willing to implement anything reasonable but since i hardly use such
>> math i only act on 'i want to achieve this' kind of specs (i have no time
>> to read tons of tex documents)
>
> Here are features that I would want context math to have. I do not care about
> the input syntax (whether it is same as latex or not) as long as the features
> are there.
>
> [snipped]
One more request. Allow these align, gather environments to break
across a page. Allow the user some kind of customization, whether the
break can occur at a particular location or not.
--
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008
next prev parent reply other threads:[~2006-01-14 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 0:55 Kumar Appaiah
2006-01-12 8:20 ` Hans Hagen
2006-01-12 16:06 ` Aditya Mahajan
2006-01-12 17:47 ` Hans Hagen
2006-01-12 21:29 ` Aditya Mahajan
2006-01-13 17:59 ` Hans Hagen
2006-01-14 1:48 ` Aditya Mahajan
2006-01-14 8:36 ` Aditya Mahajan [this message]
2006-01-14 16:58 ` Adam Duck
2006-01-14 17:04 ` Aditya Mahajan
2006-01-14 9:47 ` Tobias Burnus
2006-01-15 17:27 ` 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=Pine.WNT.4.63.0601140334040.2476@nqvgln \
--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).