From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \| should give two || and not one
Date: Tue, 19 Feb 2013 13:09:38 +0100 [thread overview]
Message-ID: <CALBOmsYRhWBYhWQ6bENm29Hrjpo29P5jCWLtTke2p7D3wVUxkw@mail.gmail.com> (raw)
In-Reply-To: <5123460F.70300@wxs.nl>
On Tue, Feb 19, 2013 at 10:29 AM, Hans Hagen wrote:
> On 2/19/2013 8:36 AM, Keith J. Schultz wrote:
>>
>> Hi All,
>>
>> In a way, it is correct that for compatibility reasons and and convert
>> it is good to keep the old syntax.
>>
>> Yet, ConTeXt is suppose to be more natural.
>
> I consider the \{ \} \| etc to be escapes for tex characters. In fact, if
> one wants || in math then it's more natural to support || directly.
Except that braces actually need an escape, while bars don't. I don't
see any advantage of "\|" representing a single vertical bar, it only
breaks compatibility and helps confuse those who used "\|" in other
flavours of TeX. There is a nice thread on SX:
http://tex.stackexchange.com/questions/498/mid-vert-lvert-rvert
As others have already written, one should use the appropriate unicode
character, not two bars. (Two bars are a separate symbol - I guess
that you probably don't want to recognise two subsequent bars are
replace them with a different glyph?) And even then there is a problem
with typographical conventions: whether the symbol is used as
left/right delimiter, as a binary operator, ...
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:[~2013-02-19 12:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 10:14 Mikael P. Sundqvist
2013-02-15 12:42 ` Wim W. Wilhelm
2013-02-15 12:55 ` Mikael P. Sundqvist
2013-02-15 15:26 ` Wim W. Wilhelm
2013-02-15 15:37 ` Mikael P. Sundqvist
2013-02-15 15:47 ` Mikael P. Sundqvist
2013-02-15 16:19 ` luigi scarso
2013-02-18 9:23 ` Mikael P. Sundqvist
2013-02-18 9:42 ` luigi scarso
2013-02-18 9:51 ` Mikael P. Sundqvist
2013-02-19 7:36 ` Keith J. Schultz
2013-02-19 9:29 ` Hans Hagen
2013-02-19 9:50 ` Mikael P. Sundqvist
2013-02-19 10:56 ` Keith J. Schultz
2013-02-19 11:06 ` luigi scarso
2013-02-19 12:09 ` Mojca Miklavec [this message]
2013-02-19 14:00 ` Hans Hagen
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=CALBOmsYRhWBYhWQ6bENm29Hrjpo29P5jCWLtTke2p7D3wVUxkw@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).