Re: [PATCH] input charset not initialized correctly on Win32

Petr Pajas <[email protected]>
Newsgroups gmane.comp.lang.perl.tk
Organization UFAL MFF UK
Message-ID <[email protected]>
On Tuesday 06 December 2005 01:42, Slaven Rezic wrote:
> Petr Pajas <[email protected]> writes:
> > Hi Nick, All,
> >
> > I found that Windows users of my Tk-804 based app who have Czech
> > keyboard (CS) set as *default* can't input Czech characters into input
> > entries until they switch from CS->EN->CS using the Alt+Shift
> > Windows shortcut (until they do, messy characters appear on the screen
> > instead). After the switching to EN and back everything works fine (it
> > also works fine if EN keyboard layout is the default and the user
> > switches to CZ when the app starts).
> >
> > Going through the win32 sources, I easily identified the problem
> > in pTk/mTk/win/tkWinX.c. The best patch I could manage is attached.
> >
> > Here's what happens: Tk tracks keyboard layout switches by listening to
> > the Win32 WM_INPUTLANGCHANGE event in order to keep its info about the
> > current input encoding up-to-date. The problem is, that it doesn't
> > initialize its internal variables according to the initial layout
> > (probably assuming its always EN).
> >
> > Please have a look at the patch and consider applying it. The patch is
> > against the latest CPAN release (Tk-804.027).
> >
> > Also, does is this file taken from Tcl/Tk? Should I contact those guys
> > too?
>
> Yes and yes.
>
> Regards,
>         Slaven

Ok, thanks. Reported as 
http://sourceforge.net/tracker/index.php?func=detail&aid=1374119&group_id=12997&atid=312997
(patch against tcl/tk codebase attached to the report).

Cheers,
-- Petr
-++**==--++**==--++**==--++**==--++**==--++**==--++**==
This message was posted through the Stanford campus mailing list
server.  If you wish to unsubscribe from this mailing list, send the
message body of "unsubscribe ptk" to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.