JDK-4136003 : Spec for java.text and java.util needs to specify required locale
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.text
  • Affected Version: 1.2.0,1.3.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,solaris_2.5
  • CPU: generic,sparc
  • Submitted: 1998-05-07
  • Updated: 2017-05-16
  • Resolved: 2004-09-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
Other
5.0 b28Fixed
Related Reports
Duplicate :  
Description
Name: mgC56079			Date: 05/07/98



The specification for

  java.util.Locale.getAvailableLocales() 
  java.text.BreakIterator.getAvailableLocales() 
  java.text.Collator.getAvailableLocales() 
  java.text.DateFormat.getAvailableLocales() 
  java.text.DecimalFormat.getAvailableLocales() 
  java.text.Format.getAvailableLocales() 
  java.text.NumberFormat.getAvailableLocales() 

should be updated. 
It should explicitly say that Locale.ENGLISH is a core locale and is 
guaranteed to be supported on any java-compatible platform.
The core locale used to be Locale.US prior to jdk1.2beta3,
however, this has been changed to Locale.ENGLISH in jdk1.2beta3 and beta4,
thus invalidating a number of JCK tests.

If this is an intended change, it should be reflected in documentation.

======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger tiger-beta FIXED IN: tiger-beta INTEGRATED IN: tiger-b28 tiger-beta VERIFIED IN: 1.5.0_01
2004-09-18

EVALUATION Both Locale.US and Locale.ENGLISH are core locales. Is there still a problem? I'm closing this assuming this means there's no problem. alan.liu@eng 1998-08-05 I did a search on JDK 1.3 javadoc and haven't found any explicit statement that Locale.US and/or Locale.ENGLISH are required by any conformant implementation. As a result, quite a few TCK tests are now challenged and will probably be invalidated. Could you please evaluate this issue and let us know whether there is at least one mandatory locale, or licensee has a full freedom in implementing whatever locales he wants? stanislav.avzan@eng 2000-05-10 Another issue is that if Locale.US and/or Locale.ENGLISH are mandatory, are their items and/or contents a public interface? masayoshi.okutsu@Eng 2000-05-11 Name: nl37777 Date: 10/24/2003 Added requirement "The array returned must contain at least a Locale instance equal to Locale.US." to the specifications of the getAvailableLocales methods in java.util.Locale, java.util.Calendar, java.text.BreakIterator, java.text.Collator, java.text.DateFormat, and java.text.NumberFormat. The classes java.text.Format and java.text.DecimalFormat, which are mentioned in the description, don't have such a method. ======================================================================
2004-09-18