Is this a question or bug report? If so, what is the actual question or bug report?
Turkish language does not
Komut yardýmý için #Help kanalýný, teknik yardým için
#OperHelp kanalýný kullanýnýz.
No such nick/channel Turkish niçk
Read
this for information about mIRC 7.x and the change to unicode. In short, you should start using unicode instead of code pages. It works far better and Turkish and all other languages work with unicode in mIRC 7.x without having to worry about changing code pages. There are ways to work with code pages in mIRC 7.x, but they are going to be cumbersome in the long run. If you really have to use code pages (not recommended), then you'll have to stick to mIRC 6.35. Code pages will not be supported in the current or any future release of mIRC.
the use of Turkish language version will be a problem as I understand v7
umutederim gets up in the future, this problem
Thank you to all of you
It is not a problem if you use Unicode instead of code pages. If you don't use Unicode, then you won't be able to upgrade mIRC beyond 6.35 unless you want to try the somewhat troublesome methods of scripting code page support. Khaled has stated that there aren't any plans to provide code page support in mIRC anymore. After Unicode being available for a very long time, it's time for people to start making use of it. It's much superior to code pages.
It is not a problem if you use Unicode instead of code pages. If you don't use Unicode, then you won't be able to upgrade mIRC beyond 6.35 unless you want to try the somewhat troublesome methods of scripting code page support. Khaled has stated that there aren't any plans to provide code page support in mIRC anymore. After Unicode being available for a very long time, it's time for people to start making use of it. It's much superior to code pages.
How are people supposed to make use of it if it's only supported by 2 out of 3 users (wild guess)? You need to fall back to code pages or else NO one will migrate away... no one will upgrade because it's the only way to be sure you you can still communicate with people who don't support it yet. And people will just end up refusing to upgrade at all if it means they can't communicate anymore.
The majority of IRC clients support it and have supported it for a very long time. mIRC has supported sending and receiving unicode text for a long time. People on older version don't even have to upgrade. They can just change their options to start sending text and receiving it in unicode. Other clients can also change their options without requiring upgrading to newer clients if the person doesn't want to. Obviously, there's a cutoff if you go back enough versions, but catering to people who use a 10 year old version of a client is not worth it.
In most cases, all it really takes is for channel ops/admins/owners/etc to choose to switch to a Unicode channel name (if needed) and ask their users to switch to unicode encoding. All it takes from users is to change their settings or upgrade.
The only time it will be more of a problem is if the server doesn't support unicode. Just because a server uses code pages doesn't mean it doesn't support unicode. But, for those that don't, then the users will be stuck on older clients or other clients until/if the server upgrades to support unicode.
The refusal to change is a common problem everywhere. That doesn't mean that those who are willing to accept change can't do so. Change doesn't have to cater to those who refuse to change. That may not be the nicest stance on the issue, but it's true nonetheless. If Khaled feels that unicode is a better option and wants to avoid continuing to confuse the issue as it was in the past when mIRC did support both options, then it's his choice. The download numbers support the fact that mIRC will remain very popular and that many people will end up switching to unicode just to keep using the newest version of mIRC. For anyone who doesn't want to use unicode, there's nothing wrong with 6.35.