Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 108931 - LTC5226-Unicode Supplementary Support required
LTC5226-Unicode Supplementary Support required
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: glibc (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-11-03 10:03 EST by IBM Bug Proxy
Modified: 2007-11-30 17:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-20 18:34:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description IBM Bug Proxy 2003-11-03 10:03:03 EST
The following has be reported by IBM LTC:  
Unicode Supplementary Support required
IBM products are currently required to support Unicode Supplementary 
Characters.  RHEL 3 currently doesn't have this, so we are asking if
it can be 
added in.

This will also be a requirement for RHEL 4.
Comment 1 Jakub Jelinek 2003-11-03 10:31:13 EST
I think you need to specify exactly what doesn't work for you.
wchar_t is 32-bit on all arches supported by us, various iconv
conversion modules clearly support surrogate characters
(e.g. UTF-16, UTF-8, UTF-7 etc.).
So what exactly do you mean by that support? We don't AFAIK
ship fonts with those characters (but I'm not sure if we even cover
the whole standard plane).
Comment 2 Ulrich Drepper 2003-11-20 12:46:25 EST
Ping.  We need specifics.  Otherwise I'll close this bug.
Comment 3 IBM Bug Proxy 2003-11-20 18:28:35 EST
------ Additional Comments From cycheng@ca.ibm.com  2003-20-11 14:49 -------
I suggest closing this bug for the time being. Once we have the specifics, we
can open a new bug to track them. Thanks. 
Comment 4 Ulrich Drepper 2003-11-20 18:34:24 EST
No information -> no change.

Note You need to log in before you can comment on or make changes to this bug.