Em seg, 04 set 2000, Geoffrey Lee escreveu:
> >
> > Hello
> >
> > I've tried some time ago the cooker Postgres 7.0.2-3mdk. As it asks
> > for Tcl/Tk 8.3.2, I updated my original Tcl/Tk 3.0.5 version included in
> > Mandrake 7.1. After that, I could not insert accented characters into any entry
> > of any Tcl/Tk application, which includes VTcl, Pgaccess, and so forth. After
> > some research, I discovered that Tcl/Tk 8.4 will probably solve this bug. If
> > that is correct, the Tcl/Tk packages included in Mandrake 7.2 beta probably
> > will cause the same problems. Or, are there a fix to this bug?
> >
>
> Yes but for now I don't want to include 8.4 at this moment since all the tcltk
> apps would need to be recompiled, considering that we are in freeze ... besides
> 8.4 is in alpha state. Since I use an English system, I can't reproduce this
> one ... if you can give me some instructions on how to reproduce the bug then
> I can take a look at it to see if I can fix anything ..
>
> --
> Geoff
--
Geoff
To reproduce the error I figure out that you may use any keyboard settings that
use a dead key to produce accented characthers. I am a Brazilian-Portuguese
user and my keyboard is configured as us-international kb (see, it is not a
Brazilian or Portuguese kb). I don't know if locales has anything to do with the
problem. I don't think so, but as an info, my system runs under
Brazilian-locales (pt_Br). The bug happens when you type any accent following
by a letter into a entry widget: for instance, you will get an "~a" instead an
"�". You can try to reproduce it in Pgaccess, Visual Tcl, or anything that has
a Tcl/Tk entry widget. Try it and tell me if you got it.
I found some info about a patch or a fix (to Czech language) at Tcl/Tk site and
in the related newsgroup (sorry, but I can't remember where). As I feel it
somewhat complicated to patch my system just now, I reinstaled the old Tcl/Tk
and Postgres. Anyway, I think that this problem will affect other accented
languages users, so I posted my experience to alert you, also hoping that
someone has a easy soluction to this bug.
Cheers
S�rvio T�lio Pires Amarante
[EMAIL PROTECTED]
