JDK-4221795 : [Nor] RFE: Please make java.text.Normalizer a public class
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.text
  • Affected Version: 1.1.2,1.2.0,1.3.0,5.0,6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,windows_nt
  • CPU: generic,x86
  • Submitted: 1999-03-18
  • Updated: 2017-05-16
  • Resolved: 2005-05-23
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 Availability Release.

To download the current JDK release, click here.
6 b38Fixed
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Name: krT82822			Date: 03/18/99

java.text.Normalizer has some useful class methods such as:

public static String decompose(String input);
public static void decompose(StringBuffer buffer);
public static String compose(String input);
public static void compose(StringBuffer buffer);

Unfortunately, however, java.text.Normalizer is not public class,
so these methods cannot be accessed from user's code.

Users(including me) should be able to use these methods to implement their own text processors (for example, I18N versions of regexp
library or multilingual search engines).
(Review ID: 55696)

Name: nl37777			Date: 06/14/2004

According to ###@###.###, support for the 
normalization forms D, KC, and KD is required.
###@###.### 10/28/04 01:11 GMT

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang

WORK AROUND Name: krT82822 Date: 03/18/99 Copy the entire code into user's package, or re-invent wheels. ======================================================================

EVALUATION Appears to be a relatively low-risk enhancement. Will continue to evaluate with feedback from others. Name: nl37777 Date: 05/05/2003 Additional functionality has surfaced that would benefit from a public Normalizer: - The Character Model for the World Wide Web (http://www.w3.org/TR/charmod/) relies on Normalization Form C. - The XML specification (http://www.w3.org/TR/xml11/#sec2.13) says that parsed entities should be in normalized form according to the Character Model. - The specification of International Domain Names, in particular RFC 3491, requires normalization form KC as of Unicode 3.2. ====================================================================== Target for Mustang ###@###.### 2004-07-27