From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: comma as decimal point: bug? Date: Mon, 27 Aug 2012 12:09:23 -0400 Message-ID: <26130.1346083763@alphaville> References: <87r4qt9xrf.fsf@gmail.com> <2012-08-27T17-40-09@devnull.Karl-Voit.at> Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36565) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T61sW-0002zU-Ae for emacs-orgmode@gnu.org; Mon, 27 Aug 2012 12:09:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T61sV-0003Z1-6J for emacs-orgmode@gnu.org; Mon, 27 Aug 2012 12:09:28 -0400 Received: from g6t0184.atlanta.hp.com ([15.193.32.61]:23766) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T61sV-0003Ym-18 for emacs-orgmode@gnu.org; Mon, 27 Aug 2012 12:09:27 -0400 In-Reply-To: Message from Karl Voit of "Mon\, 27 Aug 2012 17\:44\:51 +0200." <2012-08-27T17-40-09@devnull.Karl-Voit.at> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: news1142@Karl-Voit.at Cc: emacs-orgmode@gnu.org Karl Voit wrote: > * Nicolas Goaziou wrote: > > > > Rainer Thiel writes: > > > >> I have seen that as of v. 7.9, org tables are supposed to accept > >> commas as decimal points which is useful if you set up tables to be > >> used in in files where continental conventions are expected to be > >> followed. > > > > Actually, this more subtle. Tables recognize numbers with a comma as the > > decimal mark. But it only means such numbers will be properly aligned to > > the right. Internally, calculations still require dot separator. >=20 > When I read the change-list of Org, I bet that there *will* be > problems because of this cosmetic change :-) >=20 > From user experience perspective, it is quite clear that =C2=ABOrg > recognizes numbers with commas=C2=BB will be mixed up with =C2=ABOrg can > calculate with numbers containing commas=C2=BB. You can not make this > clear - even with renaming the settings variable. >=20 > Although I totally understand that numbers with commas should be > made possible (I am a German speaking guy) I guess there will be > even more issues in the future as long as cosmetics and > functionality is not aligned. >=20 Agreed, but IIUC the main problem is that org depends on calc for the calculations and calc is firmly in the "decimal point MUST be a period" camp. So the cosmetics/functionality alignment would involve surgery on calc, something that nobody should undertake lightly - if at all :-). I believe the above statement is correct but if anybody has better information, please correct me. Nick