Bug 3137 - german country code creates a floating-point number problem
Summary: german country code creates a floating-point number problem
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 5.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
Depends on:
Reported: 2012-01-30 09:54 UTC by p.lutz
Modified: 2012-02-01 10:53 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

code.txt to floating-point numbers (148 bytes, text/plain)
2012-01-30 09:54 UTC, p.lutz

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description p.lutz 2012-01-30 09:54:47 UTC
Created attachment 1290 [details]
code.txt to floating-point numbers

If there is the setup of the iPad to a german country code, the system will produce a problem with floating-point numbers. Instead of a "dot", we found a "comma" (decimal point) at serialisation.
Comment 1 Sebastien Pouliot 2012-01-30 16:43:57 UTC
Just to be clear the attached code returns a ',' if the iPad is configured to display German ?

and there are no, application specific, culture being used, right ?
Comment 2 Sebastien Pouliot 2012-01-30 16:46:11 UTC
ok, I can duplicate the issue
Comment 3 Sebastien Pouliot 2012-01-30 18:12:24 UTC
note: this bug also exists in mono master
Comment 4 Sebastien Pouliot 2012-01-30 19:00:50 UTC
Fixed in Mono (master and mono-2-10) and MonoTouch (master)
Thanks for the test case.
Comment 5 p.lutz 2012-02-01 10:07:56 UTC
Hello Sebastien, 
thanks a lot for the fast fixing. Please, could you told me the availability of the Release 2-10? Thanks in advance.

Kind Regards,
Comment 6 Sebastien Pouliot 2012-02-01 10:53:30 UTC
Sorry I can only tell you where the fixes are committed and, if not reverted (e.g. regressions), in which version they _should_ be available (i.e. 90% accuracy ;-). In this case the fix should be in MonoTouch 5.2.2 and should also be part of the next Mono 2.10.x.

However I don't know when they will be released (many other things, like QA and packaging and other projects affect release dates). You might want to ask support@xamarin.com to see if they know or can give you a "guesstimate".

note: please do not re-open bugs unless a regression is found (i.e. the original test case fails again :-)