Wrong coordinates generation at some non-english locales
Brought to you by:
boseefus00001
Wrong coordinates are generated at some non-english locales if locale used comma instead of point as a separator.
Methods ToKML and ToTuple of class geCoordinates generate string of coordinates separated by comma and write it to KML file or return it.
If locale (russian as sample) used comma (instead of point) as a separator of two parts of number, then generated string is incorrect, because of all additional commas.
I'm temporarily fix the problem by replacing all calls of ToString() without parameters in ToKML and ToTuple methods to the calls of ToString with parameter System.Globalization.CultureInfo.InvariantCulture
Logged In: YES
user_id=1516276
Originator: NO
Currently researching areas in ge-kml that use ToStrings() that might be affected byt CultureInfo.
Logged In: YES
user_id=1516276
Originator: NO
Fixed in version 2.1.0.6