You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Luc Vanlerberghe (JIRA)" <ji...@apache.org> on 2012/05/31 15:32:23 UTC
[jira] [Updated] (LUCENENET-493) Make lucene.net culture
insensitive (like the java version)
[ https://issues.apache.org/jira/browse/LUCENENET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luc Vanlerberghe updated LUCENENET-493:
---------------------------------------
Attachment: Lucenenet-493.patch
Makes lucene.net locale/culture independent (like the java version).
Solves a few testcases that fail when run on a machine with a non-US culture.
> Make lucene.net culture insensitive (like the java version)
> -----------------------------------------------------------
>
> Key: LUCENENET-493
> URL: https://issues.apache.org/jira/browse/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
> Labels: patch
> Fix For: Lucene.Net 3.0.3
>
> Attachments: Lucenenet-493.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira