I am aware that mIRC is not 100% unicode compliant.
For example
//if (ô == Ô) echo -ag ok
is false.
I'm also aware this particular issue/example above with case folding is on the to-do list
case folding &
on the todo list, maybe argv0 could help you there.
Now in unicode, it's possible to render the same character using different bytes:
caf\u00E9 and cafe\u0301 should both be "café".
With the font consolas, both are displayed correctly as "café".
With the font fixedsys (which does have the glyph for 'é', no font-linking should be applied?), the \u0301 version does not show "café", just "cafe", is this a bug or am I missing something?
This topic also implies unicode normalization, to be able to compare the string caf\u00E9 and cafe\u0301, we need unicode normalization, is this also on the to do list somewhere? I can see you're pretty busy with adding multi language support in mIRC but multi-language is related to unicode somehow, I believe it would be a good idea to get mIRC to be more unicode compliant first.
