ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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 16:08:41 +0200	[thread overview]
Message-ID: <7C75731E-F17F-4EE0-972A-7A5CECE81BDB@telia.com> (raw)
In-Reply-To: <55B23DAF.7080704@wxs.nl>


> On 24 Jul 2015, at 15:29, Hans Hagen <pragma@wxs.nl> wrote:
> 
> On 7/24/2015 2:32 PM, Hans Aberg wrote:
>> [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.
> 
> i don't understand what you mean as the issue is not unicode or ascii but categorizing symbols in classes

Right, but that has in part already been done by Unicode. It is not really possible to classify math symbols from the the mathematical point of view, as every author in principle use their own notation.

> when we have a symbol in the input (can be a : but also something else) in some cases it is a binary but in other cases a relation or whatever

Right. When TeX was written, there was only ASCII, so Knuth set “:” to the ratio binary operator, and the function “:” to \colon.

Now, when Unicode is available, it sets the ratio binary operator to  ≔ COLON EQUALS U+2254, leaving : COLON U+003A open for other uses. So set the latter to \colon, and add a command \ratio for the former.

> this influences the spacing and the 'domain' (or dictionaries) group symbols so that we can assign the right properties
> 
> entering a utf sequence representing 0x2236 still doesn't always prescribe what mathclass it is, 0x22A5 0x22C5 0x25B3 are examples of such dual face characters
> 
> (this is actually more important in for instance xml input)

I was thinking of just having the two, \colon and \ratio. Looking into some books before electronic typesetting, the spacing of the latter can vary widely: some do not use spaces at all. So a set might look
  {x:x < a}
instead of
  {x : x < a}
But that would be a typographical issue, rather than semantic.

___________________________________________________________________________________
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:[~2015-07-24 14:08 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
2015-07-24 13:29         ` Hans Hagen
2015-07-24 14:08           ` Hans Aberg [this message]
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=7C75731E-F17F-4EE0-972A-7A5CECE81BDB@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).