After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 118792 - non-BMP unicode characters (i.e. planes besides plane 0
non-BMP unicode characters (i.e. planes besides plane 0
Status: RESOLVED DUPLICATE of bug 101081
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other other
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2003-07-31 18:53 UTC by Trever Adams
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Trever Adams 2003-07-31 18:53:07 UTC 
Package: gtk+
Severity: normal
Version: GNOME2.2.2 2.2.2
os_details: GNOME.Org
Synopsis: non-BMP unicode characters (i.e. planes besides plane 0
Bugzilla-Product: gtk+
Bugzilla-Component: gtk
Description:
Description of Problem:
Mozilla now at least displays plane 1 and plane 15 characters in Linux. 
It is my understanding that it has to work around the same problems with
X (i.e. 16 bit fonts), but still does it.

Is this possible to do with GTK at least until some X fixes can be made?
  I need these fonts for scholarly and other reasons.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-31 14:53 -------

Reassigning to the default owner of the component, gtk-bugs@gtk.org.
Comment 1 Owen Taylor 2003-07-31 19:00:56 UTC 
You can get it more-or-less working with a one-line change
to Pango; we expect to have it fully working out of the
box for Pango-1.4/GTK+-2.4

*** This bug has been marked as a duplicate of 101081 ***