Missing the point here. ('point'
)
The problem is not the list separator.
Here we use a comma as decimal separator.
49,99€ (about fifty Euros)
1.000,00kg (one thousand kg or one ton, correct up to 2 decimal digits)
129,12345mm (about one hundred and thirty mm, with 5 decimal digits)
pi = 3,14159...
g = 9,81m/s²
e = 2,718281828459045...
Entering '1.1258' as a number will result in a value of over eleven thousand or an error.
(The misplacement of the grouping separator may be ignored)
If you don't believe me, take a look here:
https://en.wikipedia.org/wiki/Decimal_separator
On a map that is half & half, 11 different symbols are used worldwide.
Correlate this with the use of the metric/Imperial system and you get a very colorful map.
John Hyslop wrote: ↑Thu Aug 06, 2020 5:17 am
Both Metric & Imperial Systems by DEFAULT use commas " , " as the coordinate separator
This quote is only true for about half of the world population because they have the comma as decimal separator.
Born in Belgium we are used to distinguishing that at glance. Mistakes are costly.
Our mind is constantly evaluating the real value of a number in its native system.
11.234 in mm doesn't make sense in a drawing of car, that would be over 11 meters or a very big car.
Before the age of 18 we take on our 3e language, leaving the educational system we understand 4-6 languages by standard.
If we got a technical education it gets worse, standards, normalization's,
different numerical systems, numerous applications and programming languages.
Aviation and military avoid this by saying the word 'decimal' in full.
eg. 'Frequency one .. two .. three .. decimal .. eight .. two' (123,82 for us or 123.82 for others)
Using a ',' (comma) for decimal separator.
Using a '.' (point, full stop) for digit grouping.
We don't have the option to use a ',' (comma) as list separator.
So, we have to use a semi-colon ';' as list separator.
And we use both in correct writing:
-This is a list: one, two, three.
-This is the same valid list: one; two; three.
But we should obey an other language native form.
Most, All good applications handle this.
And yes, A CSV (Comma Separated Value) is separated by semi-colons over here.
(an SCSV then
)
Further, the dot on our numerical keyboard spits out a ',' (comma) by default.
Our OS does that. Entering a dot as comma is a bit harder: Shift+[;|.]key.
For almost every value we enter!
I try to use this in this forum by default but sometimes a comma slips trough.
The biggest hurdle is that most programming language use a dot as decimal separator.
C++ , Java , JavaScript ... again very prone to errors even critical.
QCAD fails at some points here:
In the status bar the use of a dot for decimal separator is persistent.
> The preference list separator is used, the decimal separator NOT.
In the property editor the use of a dot for decimal separator is persistent.
> Useally no list separators are needed.
Dimensions are formatted correct. Thumbs up.
Info ... Position will display the same as the status bar.
> Clicking will parse that 'as is' to the command history, eg. '-2.315846;2.010214'
Entering values depend on whether the input field is made 'smarter'.
At some places we can enter single values as 3,14159 or 3.14159 but in standard that would be a 'dot'.
The command line is one of such places.
Entering a list in the command line is strictly separated with semi-colon.
The bad thing that we can't copy values from fields with a dot and paste it where the use of a comma is strict.
Aside QCAD, I always keep Notepad open: copy, paste, alter, (copy, paste, alter, group), cut/copy, paste.
Another bad thing is that we have to avoid the decimal key of our numerical key pad.
I do understand why people that always had but one system to cope with are troubled.
I forgive John faulty statements.
Even Andrew calls it a mess. And it is a big mess.
Regards,
CVH