[LUCENE-1846] More Locale problems in Lucene

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 2.9
• Component/s: core/other
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Uwe Schindler
• Created: 23/Aug/09 09:45
• Updated: 28/Aug/22 12:07
• Resolved: 25/Jan/11 23:10

Description

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.

Issue Links

• relates to: LUCENE-1836 Flexible QueryParser fails with local different from en_US
• relates to: LUCENE-1852 Fix remaining localization test failures in lucene