Re: iso-8859-2 characters input in GtkEntry widget

[Paul Ortyl <ortylp 3miasto net>]

On Sun, Sep 16, 2001 at 04:23:00PM -0400, Havoc Pennington wrote:
> Paul Ortyl <ortylp 3miasto net> writes:
> > Short question, because I could not find answer anywhere else:
> >
> > Does anyone know how to force app linked with gtk+-1.2.10 to allow input of
> > iso-8859-2 characters into GtkEntry widget (iso-8859-1 works) various
> > combinations of enabling gtk, gdk locale with LC_ALL and LANG set to pl_PL
> > gave nothing.
>
> Are you calling gtk_set_locale() before gtk_init()?
>
> Havoc

I have found the problem finally...  I suppose that the locale code used by
gtk works OK.  

My keyboard (xmodmap) configuration was "wrong".  It means, that I had
configured it to send iso-8859-1 KeySyms instead of the real iso-8859-2
KeySyms -- eg. it was configured to send 'plusminus' instead of 'aogonek'
and therefore gtk application refused the 'plusminus' KeySym.

BUT it breaks my whole desktop configuration -- xterm and emacs lost
iso-8859-2 input capabilities!!!

The problem is that XLib function XLookupString returns proper strings only
for iso-8859-1 (eg. 'plusminus') but for iso-8859-2 ('aogonek') there is an empty string.
(Checked with xev)

So finally I have to use xmodmap each time I want to run properly gtk app...

It is not an gtk-specific question but does anyone knows how to globally configure
"strings" for non iso-8859-2 KeySyms (xkbsel and xmodmap seem to lack this
capability, my own XLib app using XRemapKeysym have not worked)

        Paul

-- 
Paul Ortyl <mailto:ortylp 3miasto net>
  Technical University of Gdańsk, Telecommunications Faculty
------------------------------------------------------------
For more information check http://3miasto.net/~ortylp