ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: ntg-context@ntg.nl
Subject: Re: A problem with autopunctuation
Date: Sun, 4 Nov 2012 23:03:54 +0100	[thread overview]
Message-ID: <20121104230354.4bda9aa3@aga-netbook> (raw)
In-Reply-To: <alpine.LNX.2.02.1211041624550.6831@ybpnyubfg.ybpnyqbznva>

Dnia 2012-11-04, o godz. 16:38:53
Aditya Mahajan <adityam@umich.edu> napisał(a):

> On Sun, 4 Nov 2012, Wolfgang Schuster wrote:
> 
> >
> > Am 03.11.2012 um 01:45 schrieb Marcin Borkowski
> > <mbork@wmi.amu.edu.pl>:
> >
> >> If I get it correctly, the following two formulae should render
> >> differently - and they don't.  What is going on?
> >>
> >> \setupmathematics[autopunctuation=yes]
> >>
> >> \starttext
> >>
> >> $(2,5)$ versus $(2, 5)$
> >>
> >> \stoptext
> >
> > Spaces in math mode are ignored because the spacing is controlled
> > by different rules.
> >
> > \starttext
> >
> > \m{1.2}\par
> > \m{1. 2}\par
> > \m{1 .2}\par
> > \m{1 . 2}\par
> >
> > \blank
> >
> > \m{1,2}
> >
> > \blank
> >
> > \setupmathematics[autopunctuation=yes]\m{1,2}
> >
> > \stoptext
> 
> I always thought that autopunctuation was targetted towards the
> European tradition of using comma as a decimal separator. That
> behavior can be achieved by changing a comma to be an "ord" from a
> "punctuation". However, changing the comma to an "ord" has the
> drawback that you have to explicitly add spaces when comma is needed
> as a punctuation, for example in  sets:
> 
>     \m{A = \{a,\, b,\, c\}}
> 
> Autopunctuation is supposed to get around this: if comma is followed
> by a non-space, the comma should behave like an "ord"; if it is
> followed by a space, it should behave like a "punctuation". Clearly
> that is not happening.

+1

This was exactly what I was expecting.  (In LaTeX, there's even a
package, called icomma AFAIR, which does more or less this.)  As I
often write mathematical texts in Polish, such a feature would be
*very* useful for me.  I could use \digits or \unit, but this has its
drawbacks, too.

> Aditya

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___________________________________________________________________________________
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:[~2012-11-04 22:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-03  0:45 Marcin Borkowski
2012-11-04 21:11 ` Wolfgang Schuster
2012-11-04 21:38   ` Aditya Mahajan
2012-11-04 22:03     ` Marcin Borkowski [this message]
2012-11-30 12:51       ` Sietse Brouwer
2012-11-30 12:58         ` Sietse Brouwer
2012-12-04 12:58           ` Sietse Brouwer
2012-11-03 19:04 Andres Conrado
2012-11-03 20:15 ` Marcin Borkowski
2012-11-04 10:04   ` Wolfgang Schuster
2012-11-04 21:00     ` Marcin Borkowski

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=20121104230354.4bda9aa3@aga-netbook \
    --to=mbork@wmi.amu.edu.pl \
    --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).