Strange word & line selection in the text widget?

I am using the latest CVS head (8.5.something :-)), and I have noticed
a strange behaviour with the Tk text widget. When the
widget displays non-english text (in my case gr), when I double-click
(to select a word) or tripple-click (to select a line) in the widget,
the appearence of the selected text is bizzare: from the character the
click was done the text is displayed fine, but before this character
no text is shown. Also, strange things can happen, like characters
moving around, as if text was inserted/deleted around the selection.
Anyone else seeing anything similar?

George

George Petasis wrote:
>
> I am using the latest CVS head (8.5.something :-)), and I have noticed
> a strange behaviour with the Tk text widget. When the
> widget displays non-english text (in my case gr), when I double-click
> (to select a word) or tripple-click (to select a line) in the widget,
> the appearence of the selected text is bizzare: from the character the
> click was done the text is displayed fine, but before this character
> no text is shown. Also, strange things can happen, like characters
> moving around, as if text was inserted/deleted around the selection.
> Anyone else seeing anything similar?
>
> George

Which happens only under unix (linux fedora core 3) when I enable
XFT support :-) Without XFT, everything is normal...

George

George Petasis wrote: 
>
>Which happens only under unix (linux fedora core 3) when I enable
>XFT support :-) Without XFT, everything is normal...


Filed at SourceForge, #1185640


--Joe English

>George Petasis wrote: 
>
>Filed at SourceForge, #1185640

... and fixed, I think.  Please check current CVS HEAD
and let me know if the problem persists.

(Summary of the problem: the Xft implementation was using
a strict interpretation of UTF-8, and had a bug in the error
recovery path.)


--Joe English

Joe English wrote: 
>
>
> ... and fixed, I think.  Please check current CVS HEAD
> and let me know if the problem persists.
>
> (Summary of the problem: the Xft implementation was using
> a strict interpretation of UTF-8, and had a bug in the error
> recovery path.)
>
>
> --Joe English

Yes, the problem is now fixed :-) Thanks :-)

George

Joe English wrote: 
>
>
> ... and fixed, I think.  Please check current CVS HEAD
> and let me know if the problem persists.
>
> (Summary of the problem: the Xft implementation was using
> a strict interpretation of UTF-8, and had a bug in the error
> recovery path.)
>
>
> --Joe English

Yes, the problem is now fixed :-) Thanks :-)

George