In German (I think), some locals anyway, use a comma as a decimal separator. Australia uses comma for thousands separator and decimal point for the decimal separator. I don't know about others. So I believe an attempt has been made in the units system to allow either comma or decimal point to be used as a decimal separator.
The problem is this interaction is causing a bug where the units system changes the size of objects due to the system and the units system interacting in an unexpected way......at least on my system.
Can other please test this and see if others or other locals are seeing this issue or not?
It works like this,
if you enter 9 m (9 metres) the system shows it as 9000mm (9 thousand millimetres) so far so good, the problem is that then my system displays the 9000 as 9 comma 000 (9,000) so now when I try to edit the value the units system takes the data and assumes the comma is a decimal separator, the units system then converts my 9m (9,000mm) into 9mm (9.000mm).
here is an example of how to see this issue.
create a new document, go to part design or sketcher WB, create a new sketch, insert a rectangle, set horizontal and vertical distance constraints on the horizontal and vertical edges and edit their value on creation to 9 m (9metres).
Now look at the values in the sketch and taskview constraints list, they will say 9 thousand mm (for me "9,000 mm").
Now if you try to adjust their values, as soon as you get units in edit mode it reads that 9 thousand mm as 9 decimal 000 hence only 9mm.
and if you click OK without thinking, it of course resizes the sketch.
This is my version data....my units and most other settings are at the default values.
OS: Kubuntu 14.04 LTS
Word size: 64-bit
Version: 0.14.3685 (Git)
Python version: 2.7.6
Qt version: 4.8.6
Coin version: 4.0.0a
SoQt version: 1.6.0a
OCC version: 6.7.0