JDK-4072406 : Two Proposals Related to Unicode Support
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.awt:i18n
  • Affected Version: 1.1.3
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: windows_95
  • CPU: x86
  • Submitted: 1997-08-16
  • Updated: 1998-02-23
  • Resolved: 1998-02-23
Related Reports
Relates :  
Description

Name: rlT66838			Date: 08/15/97


1) Java uses Unicode for character encoding.
But, it is my impression that even in Java 1.1, 
Java relies on the underlying operating system 
to actually produce the glyphs and that 
different OS's support different subsets of 
Unicode.  This is contrary to the idea of 
write once -- run anywhere.

The solution is to license a Unicode font and
distribute it with the base Java distribution.
Hey!  Bitstream is giving away a Unicode font 
(Cyberbit).  Please license it from them and
make it a standard part of Java.  See
www.bitstream.com/cyberbit.htm

2) It is very difficult for users to access
Unicode characters.  At best, it can be done
with \uxxxx, but this is clumsy at best.  A
better solution is to support SGML public entity
names.  This is a superset of the familiar
HTML form: "&name;", for example "α" for
the Greek letter alpha.

Java needs to provide two methods: 

String entityToUnicode(String s) which converts
  any entity names in the string into Unicode
  characters, and

String unicodeToEntity(String s) which converts
  any non-ASCII character into its entity name.

These suggestions are relatively easy to 
implement and would really open up Unicode to
Java developers and users.

Thank you for considering my request.


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

Comments
WORK AROUND Name: rlT66838 Date: 08/15/97 ======================================================================
11-06-2004

EVALUATION Part one of this request is being addressed by the 1.2 2D API. Although Java has not yet licensed the Cyberbit font, the 2D API allows users to access any Unicode fonts found on the system. We are continuing to investigate distributing fonts with the JDK but for now it is a simple matter for users to download the Cyberbit font directly. The second part of this request involves allowing non ASCII characters to be referenced more easily in Java source. We have already addressed this problem in a somewhat different way by enabling the javac compiler to accept source in many character encodings. The user should write the source code in an encoding that most conveniently represents the characters he needs. If someone really wants to support the entity name style of referring non ASCII characters, it would be a simple matter to write a source file filter to do the appropriate transformation. I do not see this being added to the javac compiler in the near future. brian.beck@Eng 1998-02-23
23-02-1998