mIRC Home    About    Download    Register    News    Help

Print Thread
#220593 19/04/10 09:13 AM
Joined: Apr 2010
Posts: 1
A
Mostly harmless
OP Offline
Mostly harmless
A
Joined: Apr 2010
Posts: 1
When i connect to server that using cp1251 i got incorrect symbols instead of cyrillic symbols

How to fix it?

Correct cyrillict symbols should look like:

Last edited by asdffdsa; 19/04/10 09:23 AM.
Joined: Oct 2003
Posts: 3,918
A
Hoopy frood
Offline
Hoopy frood
A
Joined: Oct 2003
Posts: 3,918
What version is this on?

If it's on the beta, note that the 7.x beta no longer supports non-Unicode encodings such as the cp1251 codepage. This is not a bug, this is intentional and described on http://mirc.com/beta.html

Note that as shown in your second screenshot, you can change your encoding on the server to no longer use cp1251. Instead use UTF-8. Apparently this can be done by connecting to the server on another port (you can look up more appropriate details). This would solve your issue.


- argv[0] on EFnet #mIRC
- "Life is a pointer to an integer without a cast"
Joined: Dec 2002
Posts: 5,174
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 5,174
As mentioned, this is because mIRC is now a Unicode application and will only send and receive UTF-8 encoded text. The purpose is to, ideally, make IRC as a whole non-reliant on codepages, so that everyone will be able to view all characters in all languages. In older versions of mIRC, every user had to manually configure each of their channel/query windows with a specific font and codepage to display one particular language, and this only worked for that language, so if someone came onto that channel and spoke a different language, it would appear as garbage.

That said, the above IRC server is sending a numeric that indicates your current codepage:

<- :irc.tomsk.net 222 arnie CP1251 :is now your codepage

Unfortunately it is sending it after numeric 003 and the MOTD, which both use codepage-specific text. In order for that numeric to be useful, it would need to be sent before any codepage-specific text is used, so that mIRC can convert text from that codepage to Unicode. However, even if mIRC did convert codepage-specific text, there could still be issues, such as overlap/conflict with other encodings. This is another reason why mIRC is trying to become a UTF-8-only client.

I realize this is going to be an issue - there are many networks/servers/channels that use codepage-specific encodings. I am hoping that the benefit of UTF-8, which has been supported by mIRC since 2006, will be enough of an incentive to convince many users to move away from codepages.


Link Copied to Clipboard