Re: Re: Re: Tk text widget indices.

[tos]

but strangely does not work for my text file which looks like this, if the display is set to an english font:

y.txt

]]»  **]X»]»   **]Eõ]»    ]]»»

Hmmm. Characters like these can cause unforseen behavior, because it's not ever clear whether they are taken as ESC-sequences or meta-characters.

I googled a little with your as-ttdurga-font and saw that this is a kind of indic(assamese)-script-font. I like it's pretty appearance, but i wonder whether it can be fully represented by 8-Bit-ASCII-Code.

In your code the font-declaration seems to be insignificant. This was my impression when i tested it.

Do you actual see the desired font in your Tk-script ?

I could imagine that you have to turn your line of thought in direction unicode. Therefore it's a good idea to use at least a perl-version >=5.6.1, i think.

greetings, tos

[perl_seeker]

Hi,

these fonts use ISFOC/ISCII encoding.Not the 8-bit
ASCII.Unicode encoding has been proposed for this
script, but most font creation software (e.g.
Fontographer) for this script support either ISFOC/ISO Latin/Win 3.1 etc,
but not Unicode.
I'm using Perl 5.6 which supports Unicode, but that is of
no use, since the font I use does not use Unicode encoding.

Anyhow does Unicode have anything to do with where the
problem is?......

The search function worked correctly giving the position of
the first *.The problem is I could not extract the word
next to it using the get function because of the escape
sequence/metacharcters thing.

Could we use a loop here instead of get and read each
char after the 2nd * ,one at a time until we get a
whitespace?

And yes, I can see the actual font in the Tk text widget
window on running the script.

I could read the entire contents of the window into a scalar
and do a regexp search in it, but I still need the positions
(line no, char no)of the matches found, in the window.

By the way we can do a regexp search in the search function
itself, if we use the -regex switch.
HTH