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 22:45:46 +0200	[thread overview]
Message-ID: <FE716C35-332B-414D-9CF8-8DE6299796D6@telia.com> (raw)
In-Reply-To: <55B298F1.7060101@wxs.nl>


> On 24 Jul 2015, at 21:58, Hans Hagen <pragma@wxs.nl> wrote:
> 
> On 7/24/2015 6:57 PM, Hans Aberg wrote:

>>>> The Unicode monospace characters were added by mistake, because in computer science, style does not affect semantics, as it does math. Looking into old computer science books, they do not have monospace, and a I recall a Pascal compiler on Mac OS 9 that used styled, non-monospace fonts. So a monospace font may not be strictly necessary, though current UTF-8 plain text does not look good. In Xcode, part of the reason is that one cannot choose font per Unicode code point segments.
>>> 
>>> we're not talking of the monospace math alphabet (those are already covered but the fonts) but about a monospaced font for editing and verbatim (handy for manuals explaining math typesetting)
>> 
>> Right. But it was added because it is popular in computer science to use a monospace font, though not strictly necessary from the semantic point of view.
> 
> one extra alphabet is not putting that much of a burden on tex;

It is more a curiosity, the reason they were added. It might be useful some day, say using bold monospace for keywords in programming languages.

It reminds me, in math one can use the idea that upright for constants, italic for variables. But I think in LaTeX packages mathtools and/or unicode-math, it is difficult to do that in UTF-8, because the somehow translates them to italic.

And the Unicode sans-serif mathematical styles aren’t really semantic either from the mathematical point of view, but there is a technical standard to set tensors in sans-serif, and perhaps were added because of that. Physics books seem to be bit chaotic here. In pure math, it is all serif.

> let's hope math coders don't start using the many emoticons and alike that unicode provides

From the Unicode list discussion, I think there was a fairly large number of additional symbols the poster wanted to be added. But it took a long time, via STIX, the get the current ones usable.

But as you note, any character could be in principle be used. That is how many started off.

>> So it makes me think that, instead of a monospace font for all the math characters, one  might switch to a variable-width font in the input code, as actuallye been the case in the past.
> 
> which is actually rather inconvenient for entering tables (and i'd also never use it for programming)

Indeed, but that is the only use. The obsession in computer code to align vertically.

>> All that monospace tabbing will break, that is for sure.
> 
> right and proportial makes debugging hard (and how about blockwise copying)

So possibly, there should be some replacement when using a variable width font.

For the ASCII tabbing, the tab character was originally typically interpreted as being 8 spaces wide, but that is too much for computer code with higher indentation levels. So people switched using spaces instead, successively shrinking down to 2 spaces instead of tab, which is what I use.

Unicode has a number of tab characters, but haven’t seen them in use.


___________________________________________________________________________________
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 20:45 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 [this message]
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
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=FE716C35-332B-414D-9CF8-8DE6299796D6@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).