Re: comma as decimal point: bug?

[Karl Voit <devnull@Karl-Voit.at>]

* Nick Dokos <nicholas.dokos@hp.com> wrote:
> Karl Voit <devnull@Karl-Voit.at> wrote:
>
>> 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.
>
> 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. 

Although I do not have much clue about «calc» I already assumed this
is the case.

> So the cosmetics/functionality alignment would involve surgery on
> calc, something that nobody should undertake lightly - if at all
> :-).

Totally agree.

The point is: new users and users that does not start reading
documentation before usage will not know this. And all I want to
mention is that although I myself (now) understand the reasons, I
also understand that (new) users will keep on misunderstand this
issue until the cosmetics is aligned with the functionality of
»calc«.

This results in lot of traffic on this list with bug-reports on
this.

To avoid this, normal users should not get the alignment per default
without having to read the explanation of the whole story.

This is a trade-off.

-- 
Karl Voit