1
GTSdll 1.x Support / Re: GTSdll ��� now playing encode display error
« Last post by Mercenary09 on January 25, 2012, 02:34:46 AM »short version: If someone actually fixed this small matter of a problem, it'd be cool, but if not! Oh well. Also I think it's really just mIRC's unicode on this pc or the settings when installed on this pc since 6.35 on another PC display fine (weird to me because I don't see why that would matter where it was installed, so maybe it's just settings)
I think I can't exactly fix this, anyway. Or maybe I could, but I think it's something weird with either version of mIRC installed on this pc (I had an old PC before this, and I was using 6.35 for a while and it displayed fine without all the ÃÃÃÂÂÂ if I used headers or footers that were unicode characters. I also remember installing 6.35 on this PC just to see if I still had the problem, and strangely I did (opposed to the copied over version of 6.35 from my old PC)

Just opened the 6.35 just to see for old times, and the top is with some System font, but the actual problem was the script you were able to choose was only Japanese and I switched back to Tahoma where you had romanized alphabet scripts. Unchecking UTF-8 display only garbles the unicode tags from what you np.

Well, it's not a real problem, just a curious one (for me) anyway. I just wanted the benefit of unicode characters for spacers. I just switched characters that were breaking it to something that isn't unicode since I don't think I could solve the problem of the ÂÂÂ. While it would be neat if someone else had this problem and figured out what caused it, that'd be nice, but it's just for the eyes.
I think this is just to allow the font to display unicode characters or not. I changed it to 1 and 0, and at least one of them (or both) garbed the unicode that you announced to the channel (basically it worked the same way as the top announce in the first image if you set the version higher than your current mIRC version)
I think I can't exactly fix this, anyway. Or maybe I could, but I think it's something weird with either version of mIRC installed on this pc (I had an old PC before this, and I was using 6.35 for a while and it displayed fine without all the ÃÃÃÂÂÂ if I used headers or footers that were unicode characters. I also remember installing 6.35 on this PC just to see if I still had the problem, and strangely I did (opposed to the copied over version of 6.35 from my old PC)

Just opened the 6.35 just to see for old times, and the top is with some System font, but the actual problem was the script you were able to choose was only Japanese and I switched back to Tahoma where you had romanized alphabet scripts. Unchecking UTF-8 display only garbles the unicode tags from what you np.

Well, it's not a real problem, just a curious one (for me) anyway. I just wanted the benefit of unicode characters for spacers. I just switched characters that were breaking it to something that isn't unicode since I don't think I could solve the problem of the ÂÂÂ. While it would be neat if someone else had this problem and figured out what caused it, that'd be nice, but it's just for the eyes.
Quote
But the question now is: Why is this required? I can't see an option that changes this value 2 nor do I know what this represents. I tried setting random fonts but this always resulted in a 2.
I think this is just to allow the font to display unicode characters or not. I changed it to 1 and 0, and at least one of them (or both) garbed the unicode that you announced to the channel (basically it worked the same way as the top announce in the first image if you set the version higher than your current mIRC version)