Bug 54797

Summary: With gtk+-1.2.10-11.i386.rpm package characters from other than iso-8859-1 sets are shown in wrong way
Product: [Retired] Red Hat Raw Hide Reporter: Olaf Fraczyk <olaf>
Component: gtk+Assignee: Owen Taylor <otaylor>
Status: CLOSED NOTABUG QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: high    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-11-13 15:20:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
source code explaining bug none

Description Olaf Fraczyk 2001-10-19 10:14:05 UTC 
Description of Problem:
Labels with iso-8859-2 characters are not shown at all, if we don't
initialise locale in gtk program.

Version-Release number of selected component (if applicable):
gtk+-1.2.10-11.i386.rpm

How Reproducible:
every time

Steps to Reproduce:
1. Compile attached source code

Actual Results:
Labels with iso-8859-2 characters are not shown at all

Expected Results:
Labels shown correctly.

Additional Information:
This bug is not observed in other gtk+-1.2.10 (made self, and from other
vendors e.g. ximian)
Also, in previous version of gtk+ shipped by redhat it was shown correctly
(tested for 1.2.8 and below - 1.2.9 - not tested)
Comment 1 Olaf Fraczyk 2001-10-19 10:24:21 UTC 
Created attachment 34401 [details]
source code explaining bug
Comment 2 Owen Taylor 2001-10-19 15:07:47 UTC 
It's not a bug. If you haven't initialized localized operation
you can't expect localized operation to work. :-)

If you want to reproduce the behavior from the tarball, you probably
need to compile passing the --with-native-locale flag, which
uses the native libc locale conversion code rather than
slow, inefficient, unreliable emulation done through Xlib.
Comment 3 Olaf Fraczyk 2001-11-13 15:20:06 UTC 
So the 'native libc conversion code' is more buggy ;)
Even if you initialise locale operation, the problem remains for:
locale set to "POSIX", and "C".
So it is needed to:
1. fix glibc
or
2. use "low, inefficient, unreliable emulation done through Xlib."

Regards,

Olaf
Comment 4 Owen Taylor 2001-11-13 16:19:51 UTC 
How would you expect your program to know that the high characters
in the POSIX or C locale are iso-8859-2? How does it know that
they aren't iso-8859-1, UTF-8, etc?

style->font only tells GTK+ what to use to display the string; it
still needs to know how to manipulate it before it gets to that
point. And if the locale is C or POSIX, either because gtk_set_locale()
hasn't been called or because that's the user's locale, then the
only thing it can manipulate is ASCII.