• Icon: Enhancement Enhancement
    • Resolution: Won't Fix
    • Icon: P3 P3
    • None
    • 5.0
    • core-libs
    • x86
    • windows_xp



      Name: js151677 Date: 07/08/2004


      A DESCRIPTION OF THE REQUEST :
      Recently the unicode standard has been extended to include more characters which require over more than the 16-bits that Java's String contains, hence new unicode APIs have been added to encode unicode strings into Java Strings such that 2-characters make up one unicode character.

      I humbly request that instead of adding new cluttering APIs, you simply extend String from 16-bit to 24-bit and we can continue to manipulate unicode Strings seamlessly using Java Strings.

      If you choose not to go in this direction please post an extensive description of why you made this design decision and what potential backwards-compatibility problems 24-bit Strings would cause (I can think of none).

      JUSTIFICATION :
      Minimal risk, maximum gain by making unicode manipulation seamless
      (Incident Review ID: 285121)
      ======================================================================

            nlindenbsunw Norbert Lindenberg (Inactive)
            jssunw Jitender S (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: