[fdo-users] FDO SHP + dotNet help : managing the decimal separator
dan.stoica at autodesk.com
Mon Nov 12 12:12:43 EST 2007
The LDID indicates ANSI. This is good...
I remember some discussions around decimals and I think it has been decided that setting the locale in the provider is not the way to go. The thing is SHP is self-contained when comes to localization (through LDID and CPG mechanishms). That is, it should be immune to any setlocale().
Unfortunately, you are right, this doesn't apply to decimals since atof() and sprintf() are used. I'll file a ticket in this regard to be fixed in 3.3.
I have an idea how to fix it without setting the locale in provider, but first I would like to know why it doesn't work when your application is setting the LC_NUMERIC to English... Because this would fix your particular problem in short term.
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of ytse
Sent: Friday, November 09, 2007 4:54 AM
To: fdo-users at lists.osgeo.org
Subject: RE: [fdo-users] FDO SHP + dotNet help : managing the decimal separator
Dan Stoica wrote:
> Does your dataset contain a .CPG file?
> Does your .DBF file have the LDID (Language driver ID) byte set properly
> to En?
My LDID is 0x57 and I have no CPG file.
What should I have ?
Thank you for your answer as this is a real trouble for me.
View this message in context: http://www.nabble.com/FDO-SHP-%2B-dotNet-help-%3A-managing-the-decimal-separator-tf4766129s18162.html#a13664110
Sent from the fdo-users mailing list archive at Nabble.com.
fdo-users mailing list
fdo-users at lists.osgeo.org
More information about the fdo-users