[
https://issues.apache.org/jira/browse/LUCENE-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746611#action_12746611
]
Robert Muir commented on LUCENE-1846:
-------------------------------------
Uwe, thanks for bringing this issue up!
we still have more work to do. Out of curiosity, i looked to see if the old
queryparser in core passed under korean locale.
it does not...
{noformat}
setenv ANT_ARGS "-Dargs=-Duser.language=ko -Duser.country=KR"
ant -Dtestcase=TestQueryParser test
{noformat}
> More Locale problems in Lucene
> ------------------------------
>
> Key: LUCENE-1846
> URL: https://issues.apache.org/jira/browse/LUCENE-1846
> Project: Lucene - Java
> Issue Type: Bug
> Components: Other
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Trivial
> Fix For: 2.9
>
> Attachments: LUCENE-1846.patch
>
>
> This is a followup to LUCENE-1836: I found some more Locale problems in
> Lucene with Date Formats. Even for simple date formats only consisting of
> numbers (like ISO dates), you should always give the US locale. Because the
> dates in DateTools should sort according to String.compare(), it is
> important, that the decimal digits are western ones. In some strange locales,
> this may be different. Whenever you want to format dates for internal formats
> you exspect to behave somehow, you should at least set the locale to US,
> which uses ASCII. Dates entered by users and displayed to users, should be
> formatted according to the default or a custom specified locale.
> I also looked for DecimalFormat (especially used for padding numbers), but
> found no problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
