ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Math literal colon
Date: Fri, 24 Jul 2015 21:58:41 +0200	[thread overview]
Message-ID: <55B298F1.7060101@wxs.nl> (raw)
In-Reply-To: <2F476217-416A-4BD1-9808-1B44CACC438E@telia.com>

On 7/24/2015 6:57 PM, Hans Aberg wrote:
>
>> On 24 Jul 2015, at 18:34, Hans Hagen <pragma@wxs.nl> wrote:
>>
>> On 7/24/2015 6:18 PM, Hans Aberg wrote:
>>>
>>>> On 24 Jul 2015, at 16:28, Hans Hagen <pragma@wxs.nl> wrote:
>>>>
>>>> On 7/24/2015 4:13 PM, Hans Aberg wrote:
>>>>>
>>>>> You can add it if you think it is no problem. Proper Unicode characters in the input help the readability, so putting them at high priority seems good.
>>>>
>>>> fyi, on the agenda for the gyre font project is to have a monospaced font that has most of unicode math so that we can have decent editing (once we have the funding covered)
>>>
>>> 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; let's 
hope math coders don't start using the many emoticons and alike that 
unicode provides

> 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)

> All that monospace tabbing will break, that is for sure.

right and proportial makes debugging hard (and how about blockwise copying)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | 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/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 19:58 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 [this message]
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
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=55B298F1.7060101@wxs.nl \
    --to=pragma@wxs.nl \
    --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).