lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luc Vanlerberghe (JIRA)" <>
Subject [jira] [Created] (LUCENENET-493) Make culture insensitive (like the java version)
Date Thu, 31 May 2012 13:14:23 GMT
Luc Vanlerberghe created LUCENENET-493:

             Summary: Make culture insensitive (like the java version)
                 Key: LUCENENET-493
             Project: Lucene.Net
          Issue Type: Bug
          Components: Lucene.Net Core, Lucene.Net Test
    Affects Versions: Lucene.Net 3.0.3
            Reporter: Luc Vanlerberghe
             Fix For: Lucene.Net 3.0.3

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 fail if they are not run on a machine with culture set
to US.
In the current version of 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message