From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \| should give two || and not one
Date: Tue, 19 Feb 2013 11:56:25 +0100 [thread overview]
Message-ID: <F5D75DE0-A0EC-40B4-B744-2DA12815AE06@web.de> (raw)
In-Reply-To: <CAHy-LL-21p6cRrznm4oseq9Xyk7b7G4O4RLsg3jPDKux-=SOSg@mail.gmail.com>
Hi Mikeal,
Am 19.02.2013 um 10:50 schrieb Mikael P. Sundqvist <mickep@gmail.com>:
> On Tue, Feb 19, 2013 at 10:29 AM, Hans Hagen <pragma@wxs.nl> wrote:
>>
[snip, snip]
>> a next step (already partially done) is that we organize the names in
>> dictionaries as in open math (a bit of work)
>>
>>
>>> Me, I prefer names that reflect the their functions,
>>
>>
>> me too and i wonder if we should have proper names as well i.e. use verbose
>> names as default (in char-def.lua) and define the short ones as synonyms (in
>> a tex file)
>>
>> Hans
>
[snip, snip]
> Fine. In principal I've nothing against typing || for double bars
> (even though people moving from TeX/LaTeX probably will be used to |
> for one bar and \| for two bars). Some questions:
>
> * Can one expect to get the right (that is the same as \Vert gives)
> spacing by typing || (two bars) in ConTeXt in the future?
I think we need to find a between input shortcuts and
feasiblity. One could just use unicode 02016 and \Vert.
In unicodemath you also have \Vvert for three bars.
> * Sometimes one would like to write absoulte value of z times absolute
> value of w, i.e. |z| times |w|. What if one writes |z||w|, will the
> double bar in the middle be equivalent to \Vert? (That is not wanted)
The proper way to lay this out is with a little whitspace between
the to values, so input should be |z| |w| and not as |z||w| !
> * Will it be possible to write \Bigl|| and \Bigr|| to scale both bars
> to other sizes?
> * What if one would like to have three bars with the same spacing
> between the bars as in \Vert?
See above!
regards
Keith.
___________________________________________________________________________________
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 10:56 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 [this message]
2013-02-19 11:06 ` luigi scarso
2013-02-19 12:09 ` Mojca Miklavec
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=F5D75DE0-A0EC-40B4-B744-2DA12815AE06@web.de \
--to=keithjschultz@web.de \
--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).