Comment 4 for bug 1754121

The problem still exists on the latest Windows Nightly (5.0.0-rc2-dev-262-gdfd2a8fc4). If leading zeros are suppressed and the first entry's X-coordinate actually suppresses one or two leading zeros, the format is detected as 3.2 and 3.1, respectively, instead of 3.3.

I attach a file demonstrating the problem. The file is MM 3.3 but is detected as 3.2 because the first X-value is smaller than 100.000mm.