From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Deprecated $…$ for inline math?
Date: Thu, 18 Feb 2016 21:37:55 +0100 [thread overview]
Message-ID: <CALBOmsZO8ktHTHexZLe0H4jojQedQsUyxxOaktZ3dVN_+cEdpg@mail.gmail.com> (raw)
In-Reply-To: <56C58D42.6070303@wxs.nl>
On 18 February 2016 at 10:22, Hans Hagen wrote:
>
> this brings up the question: would users (here) start using real math
> unicode input if we had a monospace math font?
On Mac (TextMate, but I assume other editors would behave the same)
the system probably does some character substitution, so as long as I
have any font that contains that particular character, I can see that
character in the editor. There is no need for a special huge font
because the system takes care of it to some extent. This is probably
different on Windows and Linux though, so I cannot say that it
wouldn't matter, it just wouldn't matter to me as long as I'm using OS
X.
I have my own keyboard with Greek letters mapped to AltGr+g+"latin
equivalent of the letter". So I always use Greek letters rather than
\alpha, \beta, ... to typeset symbols. Those are easier to read than
\controlsequences. But I probably wouldn't bother entering "unicode
math" characters for Greek letters until I would have to deal with
frequent mixes of different styles (italic, bold, ...) which would
also introduce the need for an easy input method.
I ofter use a bunch of other symbols directly (like \sim, logic
symbols, ...), but honestly I cannot imagine typesetting math
exclusively in Unicode.
Mojca
___________________________________________________________________________________
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:[~2016-02-18 20:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 8:22 Nicola
2016-02-16 8:54 ` Hans Hagen
2016-02-16 15:21 ` Alan BRASLAU
2016-02-16 15:59 ` Marco Patzer
2016-02-16 16:20 ` Hans Hagen
2016-02-16 19:12 ` Alan BRASLAU
2016-02-16 18:50 ` Aditya Mahajan
2016-02-16 19:18 ` Alan BRASLAU
2016-02-17 7:31 ` Otared Kavian
2016-02-17 9:44 ` Hans Hagen
2016-02-17 16:32 ` Alan BRASLAU
2016-02-17 18:24 ` Aditya Mahajan
2016-02-17 20:45 ` Rogers, Michael K
2016-02-17 22:18 ` Alan BRASLAU
2016-02-17 23:40 ` Pablo Rodriguez
2016-02-18 0:38 ` Alan BRASLAU
2016-02-18 9:22 ` Hans Hagen
2016-02-18 9:57 ` Marcin Borkowski
2016-02-18 20:37 ` Mojca Miklavec [this message]
2016-02-18 21:01 ` Hans Hagen
2016-02-18 9:16 ` Hans Hagen
2016-02-18 9:25 ` Meer, Hans van der
2016-02-16 16:16 ` Hans Hagen
2016-02-16 8:56 ` Marco Patzer
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=CALBOmsZO8ktHTHexZLe0H4jojQedQsUyxxOaktZ3dVN_+cEdpg@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.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).