egghelp.org community

[Reynaldo]

[TCL_no_TK]

[arfer]

[Reynaldo]

[Reynaldo]

[TCL_no_TK]

[Reynaldo]

[TCL_no_TK]

[Reynaldo]

[arfer]

Sorry about my earlier post. I should have tested first. I have no clue why it does not work. Other than possible solutions provided by TCL_no_TK methodology, the only way I can get the thing to work is by using a regexp with the actual character in question inside grouping elements ([ and ]), as follows :-

[16:27] <@arfer> % return [regexp -- {[¤]} "bla bla bla bla bla ¤"]
[16:27] <@Baal> 1

What really puzzles me is why none of the following will work :-

[16:29] <@arfer> % return [regexp -- {¤} "bla bla bla bla bla ¤"]
[16:29] <@Baal> 0

[16:29] <@arfer> % return [regexp -- {.*¤.*} "bla bla bla bla bla ¤"]
[16:29] <@Baal> 0

[16:35] <@arfer> % return [regexp -- {\xA4} "bla bla bla bla bla ¤"]
[16:35] <@Baal> 0

[16:36] <@arfer> % return [regexp -- {[\xA4]} "bla bla bla bla bla ¤"]
[16:36] <@Baal> 0

Anyway, the answer to your original query would be :-

[nml375]

This smells like a character set issue...
All four "non-working" tests evaluate to true under a simple tclsh environment for me. When pasting the same code into a telnet session (still using the very same putty setup), all ¤ are converted to $, causing the patterns with \xA4 to fail, but the others to work...

Doing something as simple as "scan [format %c 164] %c" returns 164, as expected. If I enter the ¤ into the strings and patterns using [format ...], all patterns work without a problem, including the \xA4 ones...
_________________
NML_375, idling at #eggdrop@IrcNET

[speechles]

[arfer]

Thanks guys. Thought I was going nuts there for a while.
_________________
I must have had nothing to do

[Reynaldo]

set rname "bla bla bla bla bla ¤"

[speechles]

You were already told how to make it work my man. Use "convertfrom utf-8" instead of "convertto utf-8" and it works without artifcating in those  remnants into the string.