mIRC Home    About    Download    Register    News    Help

Print Thread
,, and #256100 18/12/15 08:13 PM
Joined: Oct 2015
Posts: 15
Candent Offline OP
Pikka bird
OP Offline
Pikka bird
Joined: Oct 2015
Posts: 15
Hei,
I do not know if this is a bug.

I use server irc.estirc.net and it allows alphabet.
If someone's name is un, and I press + tab, then nothing will happen. If i write + tab it works.

Is it possible to do that: =, =, = and =.
Highlight same problem. I set my name "un". If someone says un it works. If someone says un its not highlighting.
Highlight setting: $me

I think that this is a problem in mIRC?

Last edited by Candent; 18/12/15 08:22 PM.
Re: ,, and [Re: Candent] #256101 18/12/15 08:25 PM
Joined: Jul 2006
Posts: 3,670
W
Wims Offline
Hoopy frood
Offline
Hoopy frood
W
Joined: Jul 2006
Posts: 3,670
You're correct, this is an issue with mIRC and the way it handles unicode.

Code:
//if ( == ) echo -a ok


simply does not print 'ok'.

Similar issues have been reported in the past.


Looking for a good help channel about mIRC? Check #mircscripting @ irc.swiftirc.net
Re: ,, and [Re: Wims] #256104 19/12/15 11:13 AM
Joined: Mar 2008
Posts: 89
B
BhaaL Offline
Babel fish
Offline
Babel fish
B
Joined: Mar 2008
Posts: 89
Is actually the lower-case version of (just like o is the lower-case version of O)?
One common problem with unicode and the likes is that some letters are not the same when lower-cased; mostly the turkish I is mentioned (with &#305; <-> I and i <-> &#304;).

Although, it's entirely possible that the code points actually work as upper/lower-case for those two, and I'm as wrong as mIRC here smile

Edit: oh, nvm, just tried it with the on my keyboard, and it's actually not considered equal.

Edit2: Apparently the forum software doesn't like those characters either; the &#304; turns into &#304; when I edit again)

Last edited by BhaaL; 19/12/15 11:15 AM.
Re: ,, and [Re: BhaaL] #256105 19/12/15 11:49 AM
Joined: Oct 2015
Posts: 15
Candent Offline OP
Pikka bird
OP Offline
Pikka bird
Joined: Oct 2015
Posts: 15
Originally Posted By: BhaaL
Is actually the lower-case version of (just like o is the lower-case version of O)?

Exactly.
is lower-case version of

is lower-case, is upper-case
is lower-case, is upper-case
is lower-case, is upper-case
is lower-case, is upper-case

Re: ,, and [Re: BhaaL] #256107 19/12/15 01:36 PM
Joined: Jul 2006
Posts: 3,670
W
Wims Offline
Hoopy frood
Offline
Hoopy frood
W
Joined: Jul 2006
Posts: 3,670
Yes, here is one post where the problem is fully explained http://forums.mirc.com/ubbthreads.php/ubb/showflat/Number/240374

Such a change might not be that easy to do.

Last edited by Wims; 19/12/15 01:36 PM.

Looking for a good help channel about mIRC? Check #mircscripting @ irc.swiftirc.net
Re: ,, and [Re: Wims] #256130 22/12/15 01:58 AM
Joined: Oct 2003
Posts: 3,918
A
argv0 Offline
Hoopy frood
Offline
Hoopy frood
A
Joined: Oct 2003
Posts: 3,918
It's actually not difficult, it's just a matter of calling the right APIs for string comparison:

https://msdn.microsoft.com/en-us/library/windows/desktop/dd317761(v=vs.85).aspx


- argv[0] on EFnet #mIRC
- "Life is a pointer to an integer without a cast"
Re: ,, and [Re: argv0] #256132 22/12/15 02:12 PM
Joined: Dec 2002
Posts: 4,697
Khaled Offline
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 4,697
I am aware of this issue, unfortunately it is difficult to fix as it would require changes to hundreds of routines for consistency. For example, in the hilite feature alone, changes would be required in the wildcard matching routine, the regex matching routine, the string search routine - and not just the string comparison routine. Multiply this across hundreds of other routines. Also, it is not clear cut whether Unicode normalization (and of which form) should be used everywhere, as it can have security implications. On top of that, there will be an inevitable slow down across all features where CompareString() is used, so routines that use it would need to be carefully optimized. This is on my to-do list but it is a major project. Thanks for your comments everyone.

Note: If anyone has had experience with Unicode normalization/best fit/transcoding/mapping/security issues in applications and recommended practice, your input would be appreciated.