[LUCENENET-493] Make lucene.net culture insensitive (like the java version)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Lucene.Net 3.0.3
• Fix Version/s: Lucene.Net 3.0.3
• Component/s: Lucene.Net Core, Lucene.Net Test
• Labels: patch
• Assignee: Unassigned
• Reporter: Luc Vanlerberghe
• Created: 31/May/12 13:12
• Updated: 22/Jun/12 21:53
• Resolved: 22/Jun/12 21:53

Description

In Java, conversion of the basic types to and from strings is locale (culture) independent. For localized input/output one needs to use the classes in the java.text package.
In .Net, conversion of the basic types to and from strings depends on the default Culture. Otherwise you have to specify CultureInfo.InvariantCulture explicitly.

Some of the testcases in lucene.net fail if they are not run on a machine with culture set to US.
In the current version of lucene.net there are patches here and there that try to correct for some specific cases by using string replacement (like System.Double.Parse(s.Replace(".", CultureInfo.CurrentCulture.NumberFormat.NumberDecimalSeparator)), but that seems really ugly.

I submit a patch here that removes the old workarounds and replaces them by calls to classes in the Lucene.Net.Support namespace that try to handle the conversions in a compatible way.

Issue Links

• incorporates: LUCENENET-490 QueryParser is culture-sensitive