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 103311 - UTF-8-related display problems
UTF-8-related display problems
Status: VERIFIED INCOMPLETE
Product: Gnumeric
Classification: Applications
Component: General
unspecified
Other other
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
: 103339 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-01-13 03:49 UTC by Havoc Pennington
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Havoc Pennington 2003-01-13 03:46:43 UTC 
Bugzilla-Product: gnumeric
Description:

  Please see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=79648
  for the original bug report.
   (This is a batch-forwarded bug, if it doesn't make sense let me know.
   The bug was forwarded because it's a feature request and we don't
   want to maintain the custom feature or UI change in Red Hat patches,
   or because we don't expect to fix it ourselves but thought it might be
   a legitimate issue. It was not obviously a packaging or Red Hat specific bug.
   If you would rather not be forwarded such bugs, please advise. Thanks)




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-12 22:46 -------

Reassigning to the default owner of the component, jody@gnome.org.
Comment 1 Havoc Pennington 2003-01-13 03:48:51 UTC 
Jody I think you said you weren't going to fix this in 1.0.x, but 
just wanted to forward this to confirm.
Comment 2 Jody Goldberg 2003-01-13 05:13:54 UTC 
I don't understand the thrust of this bug.  Was the current encoding utf8 ?
Although 1.0.x would definitely never be utf8 clean (backporting the 1.1.x work
is too significant a change) I don't understand why col/row headers would have
boxes in the display.  Those characters are the same in 8859-1 and utf8
Comment 3 Jody Goldberg 2003-01-13 05:26:47 UTC 
*** Bug 103339 has been marked as a duplicate of this bug. ***
Comment 4 Havoc Pennington 2003-06-04 16:57:55 UTC 
Owen can probably explain better what this is about
Comment 5 Owen Taylor 2003-06-04 18:09:40 UTC 
I think the problem was something like that the gnome-print
functions to get a GTK+ font were returning either:

 A) A font, not a fontset 

 B) A fontset, using a XLFD that Xlib doesn't know
    how how to switch charsets in ("fixed" is a common
    example)

Hard to remember at this point.
Comment 6 Jody Goldberg 2003-06-04 23:37:11 UTC 
At this point in the 1.0.x lifecycle I don't see us looking into this.