From: Hans Aberg <haberg-1@telia.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Math literal colon
Date: Fri, 24 Jul 2015 14:32:23 +0200 [thread overview]
Message-ID: <37B70C7E-510F-4323-99BF-2A488D674881@telia.com> (raw)
In-Reply-To: <55B1F7BC.7020100@wxs.nl>
[Note: I use the cc to know that I have received a reply.]
> On 24 Jul 2015, at 10:30, Hans Hagen <pragma@wxs.nl> wrote:
>
> On 7/20/2015 6:06 PM, Hans Aberg wrote:
>>> On 20 Jul 2015, at 16:40, Aditya Mahajan <adityam@umich.edu> wrote:
>>>
>>> On Mon, 20 Jul 2015, Hans Aberg wrote:
>>>
>>>> The LaTeX package unicode-math has an option colon=literal, which makes it behave as in math functions (as in example below). Has ConTeXt a similar option?
>>>
>>> No. You have to use \colon.
>>
>> It would be nice with such an option, as it helps the readability of the input files.
>
> already for some years i'm thinking of something similar to openmath dictionaries i.e. in many cases when one writes math it is in some field that is consistent within a document, say logic or engineering
>
> it is rather trivial to support something
>
> \setupmathematics[domain=logic]
>
> or so, where we automatically relate the math class with the symbols used, something that becomes more important once we start coding in unicode instead of using names
>
> but ... in order to provide this, i need information about useful categories
Unicode provides one such category. The reason is all math characters are added and in that process analyzed. I worked with Taco on that in the late 1990s.
So one main option, which might be the simplest, to assume that the input is UTF-8. Oen can the added ASCII command names, based on the Unicode names. In addition some options for special needs and legacy.
___________________________________________________________________________________
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:[~2015-07-24 12:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 12:30 Hans Aberg
2015-07-20 14:40 ` Aditya Mahajan
2015-07-20 15:43 ` Manuel Blanco
2015-07-20 15:50 ` Manuel Blanco
2015-07-20 16:09 ` Hans Aberg
2015-07-24 9:40 ` Hans Hagen
2015-07-24 12:40 ` Hans Aberg
2015-07-24 13:34 ` Hans Hagen
2015-07-24 14:13 ` Hans Aberg
2015-07-24 14:28 ` Hans Hagen
2015-07-24 16:18 ` Hans Aberg
2015-07-24 16:34 ` Hans Hagen
2015-07-24 16:57 ` Hans Aberg
2015-07-24 19:58 ` Hans Hagen
2015-07-24 20:45 ` Hans Aberg
2015-07-20 16:22 ` Hans Aberg
2015-07-20 19:34 ` Manuel Blanco
2015-07-20 20:06 ` Hans Aberg
2015-07-20 20:13 ` Hans Aberg
2015-07-24 9:43 ` Hans Hagen
2015-07-24 13:00 ` Hans Aberg
2015-07-24 13:48 ` Hans Hagen
2015-07-24 14:19 ` Hans Aberg
2015-07-24 14:29 ` Hans Hagen
2015-07-24 16:20 ` Hans Aberg
2015-07-20 16:06 ` Hans Aberg
2015-07-20 16:37 ` Aditya Mahajan
2015-07-20 17:08 ` Hans Aberg
2015-07-20 17:18 ` Hans Aberg
2015-07-20 21:29 ` Hans Aberg
2015-07-24 8:30 ` Hans Hagen
2015-07-24 12:32 ` Hans Aberg [this message]
2015-07-24 13:29 ` Hans Hagen
2015-07-24 14:08 ` Hans Aberg
2015-07-24 14:26 ` Hans Hagen
2015-07-24 16:11 ` Hans Aberg
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=37B70C7E-510F-4323-99BF-2A488D674881@telia.com \
--to=haberg-1@telia.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).