Test seperator characters in CSV import

[GoogleCodeExporter]

A user in France reported that GeoDa does not import CSV files formatted with 
the "," character for the decimal place.  GeoDa (actually the OGR reader) 
should know to use this character based on internationalization preferences for 
the user.  We need to test import of the following data sets:

POLYID, X, Y
1, "0,7777", "1,2"
2, "1001,3", "0,4"

POLYID, X, Y
1, 0.7777, 1.2
2, 1001.3, 0.4

It is not expected that GeoDa can know how to handle both automatically, but at 
least it should pick up the correct convension based on the OS (and perhaps 
calls to printf).  We might also need to provide a dialog box for CSV import 
that allows the user to choose which character to use for decimal.

Original issue reported on code.google.com by mmcc...@gmail.com on 21 Mar 2014 at 2:06

[GoogleCodeExporter]

Fixed in ci 3157 ...

Now csv locale is fully supported. Geoda will read numbers in different locale 
(can be setup via a dialog) to "C" standard locale (use "." as decimal point). 
The data will be saved using user selected locale, or sys locale if no 
selection.

Original comment by lixun...@gmail.com on 28 Mar 2014 at 9:25

• Changed state: Fixed