From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4059 Path: main.gmane.org!not-for-mail From: S2P development Newsgroups: gmane.comp.tex.context Subject: Re: Still on i18n Date: Wed, 14 Feb 2001 08:47:44 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <3A8A3820.93E6E1A@wkap.nl> References: <002901c0960f$f60d0c60$a3ccfea9@nuovo> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035394752 22495 80.91.224.250 (23 Oct 2002 17:39:12 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:39:12 +0000 (UTC) Original-To: ntg-context@ntg.nl Xref: main.gmane.org gmane.comp.tex.context:4059 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4059 Giuseppe Bilotta wrote: > > Hello, > > there's one point I would like to make on i18n: proper > support for different decimal/thousand separators; > different languages use different symbols (mostly, they swap > the meaning of comma and dot); this should be taken in > consideration esp. when typesetting math formulas, to take > care of correct spacing. Yes, but how? It should probably be done, but input syntax is very nasty. Even if $10,50$ is a number, $[10, 50]$ isn't. If somebody can think of a reasonable algorithm to decide when to do what, I'd be very happy to implement it (unf., you can't 'just' make stuff like dot and comma \active). It's not just numbers, there are some other language changes in math typesetting. Waiting for MathML in context support might be the best solution :-) Greetings, Taco