[Tcl-bugs] [ tktoolkit-Bugs-1545984 ] National language keyboards and Tk

[SourceForge.net <no...@so...>]

Bugs item #1545984, was opened at 2006-08-24 07:09
Message generated for change (Comment added) made by jenglish
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112997&aid=1545984&group_id=12997

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 69. Events
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joe English (jenglish)
Assigned to: Joe English (jenglish)
Summary: National language keyboards and Tk

Initial Comment:
Several aMSN users report problems entering non-ASCII
characters with national language keyboards.

Full thread here:
http://amsn.sourceforge.net/forums/viewtopic.php?p=9400


----------------------------------------------------------------------

>Comment By: Joe English (jenglish)
Date: 2008-03-04 12:26

Message:
Logged In: YES 
user_id=68433
Originator: YES

The first line:

./ximinfo: locale=en_DK.UTF-8

indicates that your system has LIBC support for en_DK.UTF-8 (if it didn't,
ximinfo would have printed "locale=(null)" instead).
The next line means that the X system doesn't think it supports that
locale.  (It might be client-side or server-side; the man page for
XSupportsLocale() is unclear.)

Tk doesn't even bother to test XSupportsLocale() (and it's possible that
other toolkits don't either).  Could you delete the "return EXIT_FAILURE"
line from ximinfo.c and run it again with your preferred locale?

What is XMODIFIERS normally set to?  Is it usually "@im=local", or do you
need to change this specially for Tk apps?

I can confirm that Gtk+ and other toolkits are doing _something_ different
from Tk.  I can't tell what it is though.


----------------------------------------------------------------------

Comment By: zly (zly)
Date: 2008-03-04 07:17

Message:
Logged In: YES 
user_id=1336486
Originator: NO

Thanks for commenting on this again jenglish,

My system has changed quite a lot over this period of time, and a part of
the original problem no longer applies to me.
That is, Tk applications now *does* accept the input from (most?) UTF-8
locales, but not the one I use in particular.
And the program you attached, leads to why this might be:
./ximinfo: locale=en_DK.UTF-8
./ximinfo: locale en_DK.UTF-8 not supported

My guess would be that Tk handles unsupported locales from the X server in
a different way than other toolkits, since those others still let me input
the characters.

Changing to a locale which is supported *does* let me input the characters
in Tk, and ximinfo yields the following:
./ximinfo: locale=en_US.UTF-8
./ximinfo: XSetLocaleModifiers -> @im=local
./ximinfo: style XIMPreeditNone|XIMStatusNone
./ximinfo: style XIMPreeditNothing|XIMStatusNothing

FYI my system is now openSUSE 10.3 (x86) with the following package
version:
tcl-8.4.15
tk-8.4.15
xorg-x11-7.2

----------------------------------------------------------------------

Comment By: Joe English (jenglish)
Date: 2008-03-03 11:37

Message:
Logged In: YES 
user_id=68433
Originator: YES

I might finally have a lead on this.  Unfortunately I've not been able to
replicate the problem on any machine here (Debian sarge, Ubuntu 7.04,
CentOS 5.1, various Fedora systems; tried with various locales.)

Attached program ximinfo.c prints some potentially-useful information that
might help to track this down further.

File Added: ximinfo.c

----------------------------------------------------------------------

Comment By: zly (zly)
Date: 2007-05-31 11:51

Message:
Logged In: YES 
user_id=1336486
Originator: NO

The problem persists as of Tcl/Tk 8.5a6

However, to puzzle the problem further:
Everything about my system is set up to use UTF-8, if i start wish or
another tk app (in this case amsn) defining e.g. iso8859-15 lang like
this:
>LANG=ISO-8859-15 amsn
and at the same time configures amsn to use utf-8, the input starts
working.

I can live with it like this, but it still puzzles me, what exactly goes
wrong when system is set to UTF-8.

----------------------------------------------------------------------

Comment By: Joe English (jenglish)
Date: 2006-08-24 07:12

Message:
Logged In: YES 
user_id=68433

Notes (from conversations on the tcl'ers chat with zly):
this seems to affect all Tk applications, not just aMSN.  It
does not appear to be SCIM related.  Tk 8.5, 8.4.11, and
8.4.13 are all affected (and I'm guessing the problem goes
back further than that).

One user reports that the problem appeared when upgrading
Ubuntu from Dapper to Edgy -- that's probably an important clue.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112997&aid=1545984&group_id=12997