lfs do log the messages in a ANSI-File and and all names with special signs are then just unreadable.
If you use CTRL+C to copy a name with special signs and paste it in a unicode-able text-editor, the editor receive no unicode, just ansi-code.

For example:
ﾉﾏedline ﾉﾏacing
will be called after copy and paste with LFS just:
ÉÏedline ÉÏacing

If you paste ÉÏedline ÉÏacing in "join specific game" works it fine, u will be then connected to ﾉﾏedline ﾉﾏacing

My suggestion is:
Make LFS just unicode-able or unicode compatible. Then is it lighter to find out display-names with special signs in the log-file and it is more easy to copy and paste a special signed display-name in a external application.

+100 for unicode and more language support

not exactly +100, but I'm on the side with unicode too.
Don't know how difficult/downwards-compatible it would be ..

Quote from herki :

not exactly +100, but I'm on the side with unicode too.
Don't know how difficult/downwards-compatible it would be ..

Quite difficult.

Everything runs from char's, rather than wchars (or whatever the equivilent is these days) - differently sized data types, different functions, etc.

InSim, OutSim, Outguage would need to be updated, LFS client and server, blah blah

Codepages are designed to be "easily" tacked on, giving some support, rather than none - just as they have been used.

Quote from the_angry_angel :

Quite difficult.

Everything runs from char's, rather than wchars (or whatever the equivilent is these days) - differently sized data types, different functions, etc.

InSim, OutSim, Outguage would need to be updated, LFS client and server, blah blah

Codepages are designed to be "easily" tacked on, giving some support, rather than none - just as they have been used.

Exactly what I imagined. You see the Unicode (UTF-8) problems in the IRC-networks, if one has enabled encoding and another has disabled unicode, everything gets messed up (unicode is completely 2-byte characters iirc).
But it would be the simpler way for global usability, because most eastern languages (Chinese, Japanese,..) require 2-byte characters anyway. I still got my hopes up

Quote from the_angry_angel :

InSim, OutSim, Outguage would need to be updated, LFS client and server, blah blah

Not to mention font rendering. Right now LFS just uses a lookup-texture with images of all characters in it. You cannot do that with Unicode for obvious reasons, so an actual font rendering engine would have to be incorporated. (Scawen could probably use GDI+ or something for that, but that would tie LFS even more to Windows, so I personally would rather he didn't. Freetype/Cairo perhaps if the license permits?)